Feb 28, 2025

With motor power and long-distance performance, Jeep’s all-electric 2025 Wagoneer S hits the sweet spot in the electric vehicle SUV segment. This is Jeep’s first battery-electric vehicle in their lineup, and with a combined 600 horsepower and over 300 miles of range, it doesn’t disappoint.

1. EV Motor, Power, and Performance

The standard all-wheel drive Wagoneer S is powered by a pair of electric motors: one mounted in the front and the other in the rear. Their combined output reaches 600 horsepower and 617 pound-feet of torque. The front motor has a disconnect feature that reduces electricity consumption and increases range. The Wagoneer S also has a Select-Terrain traction management system that comes in five driving modes, including Auto, Sport, Eco, Snow, and Sand.

Thanks to its powerful motors, the Wagoneer S is a lively performer. On the track it has been clocked going from 0 to 60 in 3.4 seconds and topping out at 124 miles per hour.

2. Battery, Range, Charging, and MPGe

The Wagoneer S runs on a 400-volt battery pack that can charge from 20 to 80 percent in 23 minutes using a DC fast charger. Using a 240-volt Level 2 charger, the battery should recharge from 5 to 80 percent in about 7 hours. The higher model Wagoneer S Launch Edition comes with a Level 2 home charger or $600 in public charging credits. The battery range is where the Wagoneer S really shines, with an EPA-estimated range of 303 miles. The EPA-estimated MPGe is 104 MPGe in the city and 90 MPGe on the highway.

3. Interior, Comfort, and Cargo Space

The 5-passenger Wagoneer S has a modern interior design, sporting four separate screens on the dash, amounting to a total of 45.0 inches of screen space. A 10.0-inch head-up display comes standard as does a 10.3-inch lower display for climate control. Front and rear seats are upholstered in faux-leather and the front seats come with heating and ventilation as well as massaging lumbar support. Front row leg room is noticeably ample. The rear cargo area has 30.6 cubic feet of space, which expands to 64 cubic feet of cargo volume with the rear seats folded.

4. Infotainment and Connectivity

Infotainment in the Wagoneer S is provided by four touchscreens, including a 12.3-inch instrument cluster, a center infotainment screen, and a 10.3-inch passenger screen with HDMI connectivity. Sirius XM satellite radio comes standard as does a 19-speaker McIntosh Premium Entertainment System.

5. Safety

The Wagoneer S has a host of standard driver-assist features, including lane-keeping assistance, adaptive cruise control with stopping, and predictive advanced brake assist.

Come and explore what the Jeep Wagoneer S can offer you. Contact us at Clint Bowyer Chrysler Dodge Jeep & Ram, Emporia, KS to schedule a test-drive today.

FluentNHibernate.Cfg.FluentConfigurationException: An invalid or incomplete configuration was used while creating a SessionFactory. Check PotentialReasons collection, and InnerException for more detail. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Cannot open database "dealeron" requested by the login. The login failed. Login failed for user 'default'. at Microsoft.Data.SqlClient.ConnectionPool.WaitHandleDbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.SqlClient.ConnectionPool.WaitHandleDbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 taskCompletionSource, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open() at NHibernate.Connection.DriverConnectionProvider.GetConnection(String connectionString) at NHibernate.Connection.ConnectionProvider.GetConnection() at NHibernate.Tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.Prepare() at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.GetReservedWords(Dialect dialect, IConnectionHelper connectionHelper) at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.UpdateDialectKeywords(Dialect dialect, IConnectionHelper connectionHelper) at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.Update(ISessionFactoryImplementor sessionFactory) at NHibernate.Impl.SessionFactoryImpl..ctor(Configuration cfg, IMapping mapping, Settings settings, EventListeners listeners) at NHibernate.Cfg.Configuration.BuildSessionFactory() at FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory() ClientConnectionId:f5dac539-b1c9-4f0c-888f-daf04accf3bf Error Number:4060,State:1,Class:11 --- End of inner exception stack trace --- at FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory() at SITESAA.Infrastructure.DataLayer.Contexts.DatabaseContext.LoadSessionFactory() in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.DataLayer/Contexts/DatabaseContext.cs:line 37 at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode) --- End of stack trace from previous location --- at System.Lazy`1.CreateValue() at SITESAA.Infrastructure.DataLayer.Repositories.DealerHeaderRepository.GetDealerIdByHost(String hostname) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.DataLayer/Repositories/DealerHeaderRepository.cs:line 10 at SITESAA.Infrastructure.Services.Caching.Providers.RedisCacheProvider.<>c__DisplayClass21_0`1.b__0() in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.Services/Caching/Providers/RedisCacheProvider.cs:line 81 at SITESAA.Infrastructure.Services.Caching.Providers.RedisCacheProvider.Cached[T](String key, Int32 expirationInMinutes, Func`1 functionWithPayloadWhichWillBeCached, CachingType cachingType) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.Services/Caching/Providers/RedisCacheProvider.cs:line 81 at SITESAA.Infrastructure.Services.Caching.Providers.MemoryCacheProvider.<>c__DisplayClass13_0`1.b__0() in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.Services/Caching/Providers/MemoryCacheProvider.cs:line 85 at SITESAA.Core.Helpers.Timer.Time(Action functionToBeTimed) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Core.Helpers/Timer.cs:line 21 at SITESAA.Infrastructure.Services.Caching.Providers.MemoryCacheProvider.Cached[T](String key, Int32 expirationInMinutes, Func`1 functionWithPayloadWhichWillBeCached, CachingType cachingType) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.Services/Caching/Providers/MemoryCacheProvider.cs:line 84 at SITESAA.Core.DomainServices.Caching.Providers.CacheProviderBase.Cached[T](String key, Func`1 functionWithPayloadWhichWillBeCached) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Core.DomainServices/Caching/Providers/CacheProviderBase.cs:line 37 at SITESAA.Presentation.Infra.WebRequestService.GetHostDealerId(String hostName) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Presentation.Infra/WebRequestService.cs:line 412 at SITESAA.Presentation.Infra.WebRequestService.GetDealerId() in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Presentation.Infra/WebRequestService.cs:line 192 at SITESAA.Module.CompositionRoot.ApplicationServices.<>c.b__4_0(IServiceProvider sp) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Module.CompositionRoot/ApplicationServices.cs:line 109 at ResolveService(ILEmitResolverBuilderRuntimeContext, ServiceProviderEngineScope) at ResolveService(ILEmitResolverBuilderRuntimeContext, ServiceProviderEngineScope) at ResolveService(ILEmitResolverBuilderRuntimeContext, ServiceProviderEngineScope) at ResolveService(ILEmitResolverBuilderRuntimeContext, ServiceProviderEngineScope) at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType) at lambda_method14(Closure, Object, HttpContext, IServiceProvider) at SITESAA.Presentation.Infra.Middleware.StaticDependencyInjectionShimMiddleware.InvokeAsync(HttpContext context, IDealerService dealerService, IDealerAddressService dealerAddressService, IDealerOrganizationService dealerOrganizationService, ILocationService locationService, ICustomizationService customizationService, IOemProgramService oemProgramService, IPrivacySettingsService privacySettingsService, IWebRequestService webRequestService, PlatformOptions platformOptions, IVehicleRefService vehicleRefService, CacheOptions cacheOptions, MemoryCacheProviderBase memoryCacheProvider, ICacheProvider cacheProvider, IConnectionMultiplexer connectionMultiplexer, ILoadDealerService loadDealerService, IRelayControl relayControl, IDealerFeatureRingProvider dealerFeatureRingProvider) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Presentation.Infra/Middleware/StaticDependencyInjectionShimMiddleware.cs:line 67 at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context) HEADERS ======= Accept: */* Host: prod-web-5.ashburn.edealertools.com User-Agent: Blog Loader X-Dealer-Hostname: prod-web-5.ashburn.edealertools.com