View source for Suunto Spartan Ultra

{{DISPLAYTITLE:Suunto Spartan Ultra Review}}[[File:Suunto Spartan.jpg|right|thumb|200px]]
The Suunto Spartan is an expensive but beautiful running watch. It has an elegant, simplistic physical design, combined with an effective and intuitive user interface. The materials are not only beautiful to look at, but like the ambit range before, there pleasing to the touch. Unfortunately, this beautiful design is let down by incomplete functionality and a rather hefty price tag. If you buy the Spartan, it should be predominantly because of its looks and feel, rather than its functionality. (This review is based on 1.7.30 firmware.)
=Support This Site=
{{BuyAmazon|AZID= B01I05C0LS|AZN=Suunto Spartan Ultra}}
=The Big Questions=
For a [[Best Running Watch| simple evaluation of a GPS watch]], I look at how well it can answer some basic questions. There are many things a runner might look for in a running watch, but I feel these four questions are critical. 
* '''How far did I run?''' This is the most basic question, and the Spartan has pretty good [[GPS Accuracy]]. The level of error will depend on your route, but the Spartan seems to do quite well on varied sections of my test. 
* '''How fast am I running?''' Knowing how fast you're running can be a nice to know, or it can be vital for your training or race performance. Because of the nature of GPS, watches that rely on GPS signal alone tend to have serious problems with current pace. Currently the Spartan has no support for the display of current [[Pace From A Footpod]] while getting all other data from GPS, something I find is the best option. Suunto will use its internal accelerometer when GPS signal is unavailable, but this doesn't really solve the problem. I see the current pace varying considerably from my actual pace during a run.  
* '''Where am I? '''The Spartan has a breadcrumbs display and the ability to download a course outline, but there's no "off course" warnings or directional information. There's also no "back to start" or ability to navigate to waypoints. It does have a true magnetic compass, though I've rarely found that useful in the real world.  
* '''What's my cadence? '''[[Cadence]]''' '''is one of the most critical and often overlooked aspects of running. If you get your Cadence right, many other things naturally fall into place. The Spartan will get [[Cadence]] from a [[Footpod]], and it has an internal accelerometer, though I find that's not as accurate. There are no alerts for Cadence (or any other metric.) 
For ultramarathon running the battery life of the Spartan makes it a candidate for shorter races (50 miles/100k). But if you hope to be still moving during the [[Second Dawn]], then you should look elsewhere. (You can charge the Spartan on the run, but I see that as a poor solution to the problem.) See [[Best Running Watch#Watches for Ultrarunning| Watches for Ultrarunning]] for more details.  
=Will It Be Nice When It's Finished?=
The Spartan has improved in many areas since it was first released, but it still feels incomplete. The first firmware versions I tested seemed like they were barely ready for beta testing, let alone production release. These early versions of the firmware didn't have even the most basic functionality, such as the ability to customize the displays. It seems like Suunto still have quite some distance to go before the firmware is relatively complete, and this poses a significant risk to purchasers. If Suunto were to abandon updates, as happened to the [[Garmin Epix]], you'd be left with a rather inadequate device. So, will the Spartan be a nice watch when they finally finish the updates? Predicting the future is something of a fool's errand, as nicely described in [https://www.amazon.com/dp/0143125087 The Signal and the Noise], but so far there are no indications that the Spartan will have much to justify its price tag. It is an attractive watch, made from lovely materials, and it has the highest resolution display of any watch I've tested. But beyond that these anesthetics, I don't see any functional aspects that make the Spartan a compelling purchase. There are a number of things that I feel are missing on the Spartan. 
* '''Something Novel'''. To belabor the point a little, to justify this price tag, I'd like some new feature rather than a nice display and materials. I've not found anything innovative that the Spartan provides, nor does there appear to be anything on their roadmap. 
* '''Apps'''. Suunto were the first sports watch manufacturer to allow extensibility through apps. These apps were relatively simple and nothing like the complexity and sophistication of Garmin's [[Connect IQ]], but they allowed for new functionality to be added by the community. Sadly, this functionality is not available in the Spartan, but I hope it eventually gets added in. It would be even better if they include some of the rich options that are available with Connect IQ. I've really come to appreciate the custom watch faces, new data fields, and support for niche [[Running Sensors]].
* '''Display Customization'''. With the latest firmware, you can do some customization, but it's still limited. You can't customize to add a 7-field display or a graph. 
* '''Navigation'''. There's only a primitive display of the course you load, not waypoints, off course notifications, distance to the end, backtrack, etc. 
* '''Interval Timers'''. I'm not a fan of using timers for interval training, but it's something I'd expect on watches that are far cheaper than the Spartan.
* '''Where's my phone?''' I've come to appreciate the Garmin "Where's My Phone?" feature that buzzes the phone to help you find it. It's one of the most useful bits of having a watch connected to the phone. 
* '''Stability'''. This is becoming less of a problem, and I'm not seeing a problem with existing functionality becoming broken with the latest release. 
=Physical Characteristics=
The Spartan is a big watch, though it is dwarfed by earlier devices like the [[Garmin 910XT]] which always felt like wrist mounted computers. On my minuscule wrists, the Spartan feels large, but not cumbersome or awkward. The design seems to epitomize the simplistic elegance that the Scandinavians and Finns are renowned for. There is nothing about the Spartan that indicates it's a sports watch, and I feel that it would not look out of place when worn with more formal clothing. It's a far less fussy design than the [[Garmin Fenix 3]] and like other Suunto watches, the strap is made of wonderfully soft material that feels pleasant next to the skin. Below you can see the Spartan next to some of its competitors. To the right of the Spartan is the [[Garmin Fenix 3]], which is probably closest in terms of style and tactile qualities. It's a little more rugged with its exposed bolt heads, but this also makes it a little more visually fussy. Next is the [[Garmin Epix]] that has a little more functionality than the Spartan, adding in preloaded maps which is great for navigation. As we continue to move right, the [[Polar V800]] has similar design aesthetics to the Spartan, using high-quality materials and an elegant, simplistic layout. The Polar does not have the conventional design of the Spartan but it is a beautiful watch. The polar lacks a color display, but has outstanding GPS accuracy. Finally, we have the [[Suunto Ambit3]], which is here to show an earlier (and much cheaper) offering from Suunto. 
[[File:Spartan Comparison.jpg|center|thumb|x300px|]]
Looking at these watches side on, you can get a sense of their bulk. They are surprisingly similar, and none of them could be considered thin or svelte, but they are less bulky than some of the earlier devices.
[[File:Spartan Side.jpg|center|thumb|x300px|]]
One minor feature I appreciate is the "standby backlight" which is a dim level of backlight that is always on. This makes the Spartan much easier to read indoors and dim conditions without burning through the battery. 
=User Interface=
The user interface has 3 buttons and a touchscreen, and is generally clean and intuitive. The menu system has a simple up/down/enter approach, with one of the menu options being a return to the previous level. You can use the touchscreen to navigate the menu as an alternative, but in most cases I found it easier to just use the buttons. I prefer a user interface with more buttons so that each has a specific function, but the Spartan handles things with just 3 buttons reasonably well. There are a few touch-only actions, such as a 2 finger tap to turn on and off the backlight, or pinch-to-zoom on the map. The interface is mostly responsive, though occasionally there is a slight lag. The display is much higher resolution than other watches I've tested to date, and the Spartan makes good use of this by putting more data on the screen. There are a few oddities, such as using the middle button to start a run, then the top button to pause/resume. In the scale of the infuriating user interfaces that some watches have (I'm looking at you Epson) the Spartan is a delight.
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
|- valign="top"
|[[File:Spartan Menu.jpg|none|thumb|x300px|]]
|[[File:spartan submenu.jpg|none|thumb|x300px|]]
|}
=Configuration=
Most of the configuration of the Spartan has to be done via their website and then synced to the watch. There is some configuration built-in, but not much. I generally prefer having a website for configuration as it's much easier than trying to do it on the watch, but it does mean you can't change the configuration when you're away from your computer. Most running watches have a few modes to choose from, such as running indoors or running outside, along with other sports such as cycling or swimming. The Spartan has dozens of modes with the idea that the watch would be configured more specifically. There are modes like "interval running", "race running", "track running", etc. This is an interesting approach as it allows the watch to be set up for that specific activity, displaying different information in different situations. You can also configure the sensors that are used and the GPS accuracy/battery life trade-off for each mode. Unfortunately, in their haste to release the Spartan they did not support the creation of new modes or the customization of the display. This has been partly remedied, but when you add a new custom mode, you have exactly 3 screens to configure; a 4-field display, a 5-field display, and a list of recent laps. 
[[File:SpartanConfigure.jpg|center|thumb|x200px|]] 
Based on the press releases, I believe there will be more customization in the future. Below is the 5 field display and the lap display. The display of recent laps is rather cool, as you can compare your split times, or heart rate across each lap. Or at least, it was in the last firmware; it the latest this functionality is broken. 
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
|- valign="top"
|[[File:Spartan-Run.jpg|none|thumb|x300px|This is the five field display, which you can customize.]]
|[[File:Spartan Updates A (3).jpg|none|thumb|x300px|The Spartan display can show 7 fields, which is really nice. It's more readable than I expected, but you can't customize the 7 field displays yet.]]
|- valign="top"
|[[File:Spartan Updates A (1).jpg|none|thumb|x300px|The option for an inverted display was added, and it really improves ease of reading.]]
|[[File:Spartan Updates A (4).jpg|none|thumb|x300px|Heart rate graphs are available on the predefined activities, but you can't add them to a custom layout.]]
|- valign="top"
|[[File:Spartan Updates A (2).jpg|none|thumb|x300px|Here's the graph with the inverted color scheme.]]
|[[File:Spartan-Laps.jpg|none|thumb|x300px|The lap display is a nice feature, showing you how each split is changing. There's some confusion in the Suunto software between manual laps and auto-laps (hopefully they'll clear that up.)]]
|}
=Going For A Run=
To start a run, you simply select the exercise mode, wait for the Spartan to acquire a satellite lock and a link to any sensors and then hit start. If you've synced your Spartan in the last few days, then it should acquire a satellite lock quite quickly. For my accuracy tests I always give a watch at least 5 minutes so that it can download the real satellite position information (ephemeris) rather than having it rely on the predictions it downloads during the sync. The current firmware will show when a heart rate monitor is connected, but there's no indication of the connection status for a Footpod. The Spartan display is remarkably crisp, and they put more data on the screen than other watches which can sometimes make it a little tricky to read. Like most watch displays, you sometimes have to tweak the angle so the light hits it right for optimum clarity. The Spartan has a built in the monitor, but remember this is measuring the temperature quite close to your body so it's likely to be a little inaccurate. When you finished your run, the Spartan will give a nice list of summary statistics, plus a screen of listing some averages for each lap (assuming you recorded some laps of course.) Suunto make use of heart rate analysis from Firstbeat. This means that included in the usual summary metrics are the recovery time in hours, the Peak Training Effect (PTE, a measure of workout intensity), and even an EPOC value (Excess Post-exercise Oxygen Consumption.) EPOC is an estimate of training impact, based around the elevated metabolic rate following exercise.
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
|- valign="top"
|[[File:Spartan Run (1).jpg|none|thumb|x300px|Select exercise…]]
|[[File:Spartan Run (5).jpg|none|thumb|x300px|Then choose the exercise mode..]]
|- valign="top"
|[[File: Spartan Updates A (5).jpg|none|thumb|x300px|Wait for the pointer to go solid indicating GPS lock and hit the middle button. (A firmware update added a display of connected sensors and HR.)]]
|[[File:Spartan-Run.jpg|none|thumb|x300px| The Spartan can display lots of data, though it looks to me like the distance is negative, which is confusing.]]
|- valign="top"
|[[File:Spartan Run (2).jpg|none|thumb|x300px|Pause resume is the top button, even though start was the middle.]]
|[[File:Spartan Summary.jpg|none|thumb|x300px|Lots of summary data at the end of the run,]]
|- valign="top"
|[[File:Spartan Updates A (6).jpg|none|thumb|x300px|A firmware update added a graph of altitude…]]
|[[File:Spartan Updates A (7).jpg|none|thumb|x300px|…and a graph of heart rate (if available).]]
|}
=Navigation=
The Spartan will show a breadcrumbs trail of where you've run, which can be useful for backtracking. You can also load a course into the Spartan and follow it on your run. Creating a course on the Moves Count website is fairly straightforward and intuitive, and they include a profile of the route. The Spartan makes good use of color on its map display, making it fairly easy to understand and the touch display is well used, with pinch-to-zoom or tap to zoom to an overview and back. While you can add waypoints to a course, the Spartan doesn't currently allow you to navigate to them. It won't tell you when you're off course, or how far it is to the end, or anything else you might expect if you've used a Garmin. All you get is the course outline on the display. Nor does the Spartan allow for preloaded maps, something that I'd like to see in a watch this expensive. If you want preloaded maps, then your best bet is the [[Leikr]] or the [[Garmin Epix]]. Sadly, I'm not convinced that either of those watches are being well supported by the manufacturer, so buyer beware. 
[[File:Spartan-Map.jpg|center|thumb|x300px|]]
=Sensors=
The Spartan works with the various Bluetooth heart rate monitors I tried, including the Polar H7, [[Wahoo TICKR Run]], and Suunto's own heart rate monitor. I found the heart rate monitor that is optionally packaged as with the Spartan worked fine, though I've generally used the Wahoo as I can get the heart rate data on any Ant+ watches I'm also using. The Spartan is unique in supporting the [[Stryd]] footpod, a [[Running Sensors| Running Sensor]] that will transmit "Running Power." It's nice to see these new Running Sensors supported as first-class devices, but sadly Suunto messed up their implementation. The Spartan Ultra will always calibrate a footpod against GPS, so the footpod can never be better than the GPS accuracy. In theory you could always run in indoor mode, or with GPS accuracy set to less than "best", but that's an approach that's likely to go wrong at some point. To compound the problem, the Spartan needs to pair with the Stryd as both a footpod and a power meter, and it can't do both at the same time due to Bluetooth limitations. So, you can get a power estimate from Stryd, but Stryd's ultra-accurate pace/distance information is inaccessible. The Spartan has an internal accelerometer that will give a reading for [[Cadence]] without a [[Footpod]], and I'd say this is broadly adequate but far from perfect. I tested the Spartan with the Polar Stride Sensor and the Adidas footpod and they transmitted pace and cadence information. However, the auto calibration of a Footpod limits the ability to use these devices. 
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
|- valign="top"
|[[File:Suunto HRM-front.jpg|center|thumb|x300px|The Polar H7, Wahoo, and then the Suunto HRM.]]
|[[File:Suunto HRM-back.jpg|center|thumb|x300px|The connectors for the Suunto are different to the Polar which other companies have also adopted.]]
|}
=Activity Tracking=
Like most modern running watches, the Spartan will act as an activity tracker by counting steps. This seems to be something of an afterthought with the Spartan as the standard display does not show your step of progress unless you press the middle button. The Spartan step counting seems to be reasonably in line with the other devices that I've tested. There's always some variation in the precise account, as different watches will detect or ignore small steps, especially if you doing something like cooking and moving around the kitchen rather than striding down the path on a walk. The target number of steps for the day is set on the Spartan, not the web site, which is a little confusing. There is no facility for tracking sleep, something that's routinely seen in far cheaper devices. The Spartan will track recovery time based on the [[Firstbeat]] algorithms 
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
|- valign="top"
|[[File:Spartan-StepsDay.jpg|none|thumb|x300px|A rather uninspiring display of total steps.]]
|[[File:Spartan-StepWeek.jpg|none|thumb|x300px|This weekly view of steps could have been great, but the tops are truncated at about 1.5x goal.]]
|- valign="top"
|[[File:Spartan-Recovery.jpg|none|thumb|x300px|Recovery hours tracking.]]
|[[File:Spartan-Summary.jpg|none|thumb|x300px|Summary of recent training.]]
|}
=Syncing The Spartan=
You can either sync the Spartan using a USB cable to a computer, or over Bluetooth to the smart phone app. I found that syncing to the smart phone app has been a little patchy, and I generally rely on the PC app. 
[[File:Spartan Cable.jpg|center|thumb|300px|The Spartan cable uses magnets rather than a clip to attach to the watch, and is far less fiddly than some devices, and far smaller than the vast cradles that Epson uses.]]
Syncing the Spartan will upload your workouts to their website, download information to speed up satellite lock (SGEE or Server Generated Extended Ephemeris), and to download any configuration changes you've made on the website.
[[File:MovesCount-Sync.png|center|thumb|300px|The synchronization uses a simple, lightweight application that works reasonably well.]]
=Smartphone App=
The Suunto Moves Count smart phone app for the Spartan is rather limited, and like the watch itself feels incomplete. The most obvious functional deficiency is that you can't configure the Spartan from the app; you have to go to the website. When I compare this to the Garmin app, this feels like a prototype. If you have your Spartan connected to your smartphone, you will get notifications for things like incoming texts and anything else that you have a phone notification for. You can disable the notifications while keeping your Spartan and phone linked.
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
|- valign="top"
|[[File:MovesCountApp (1).png|none|thumb|250px|The initial screen gives some rather underwhelming information. There is the amount of time you've spent in each sport, which if your runner doesn't tell you too much.]]
|- valign="top"
|[[File:MovesCountApp (5).png|none|thumb|250px|Scrolling down you see a list of each exercise, showing the time and distance. You'll notice the distance is in kilometers even though I've specified miles as my units.]]
|- valign="top"
|[[File:MovesCountApp (4).png|none|thumb|250px|If you select a specific workout you'll get a few more details on the first screen. This seems like rather poor use of screen real estate to me.]]
|- valign="top"
|[[File:MovesCountApp (2).png|none|thumb|250px|You can view some graphs of your workout, but this is not as sophisticated as the website.]]
|- valign="top"
|[[File:MovesCountApp (3).png|none|thumb|250px|One rather cool aspect to the app is the map display that shows where people have run and uploaded their workouts. I suspect this will be a great way of finding places to run in new locations.]]
|- valign="top"
|[[File:MovesCount Movie.png|none|thumb|250px|The app has the ability to create a virtual movie of your run, showing your position as a dot with a trail marking your route, while a virtual camera flies over the terrain. I'm not sure how useful this is, but it's certainly an entertaining novelty.]]
|}
=Moves Count Web Site=
I know of runners that find the Garman site more intuitive and richer in functionality than the Suunto, but I'm the opposite. I find the Move Account website to be reasonably intuitive and rich in functionality. The Suunto website exposes some interesting information from the Spartan, and provides some good analysis options. Below is the overview page from the website. I rather like the top calendar view, that shows each workout along with a vertical line indicating the duration. This gives a nice summary of your recent training, and it should give you a sense of the ratio of training to rest. The middle section shows how much time you spent in each sport, which is much use if you just run. It also includes a cross of how you felt after each workout, something you said on the Spartan after each workout. It's possible that this may be a useful tool to prevent [[Overtraining]], but I suspect it's a little too simplistic. On the right of the middle section is how long you've spent in each heart rate zone, which is another nice feature providing some high-level insight into training. At the bottom of the page is the list of workouts, which I've truncated to save space. Clicking on a workout take you to the detail page which will look at next.
[[File:Overview - Movescount.png|center|thumb|500px|]]
Here's the workout detail page in its entirety. It's too small to read, so click to view a larger image or simply scroll down as we look at each section in turn.
[[File:fellrnr_su's Running Move.png|center|thumb|500px|]]
the first section under the calendar (which will ignore as it's pretty obvious) are the summary statistics for your run. There's all the usual things you'd expect like heart rate, which includes average plus minimum and maximum, pace, calories, cadence etc., but there's also some interesting additions. Suunto license [[Firstbeat]]'s heart rate analysis so you get things like Peak Training Effect which is a measure of how intense your workout was. There's also EPOC (Excess Post-exercise Oxygen Consumption) that's an estimate of how much your metabolic rate is elevated following exercise. The Estimated VO<sub>2</sub> is also from Firstbeat, which could be estimated from your [[VO2max|V̇O<sub>2</sub>max]] and [[Maximum Heart Rate]], but few runners know their [[Maximum Heart Rate]] (which can't be calculated), let alone their [[VO2max|V̇O<sub>2</sub>max]].
[[File:MovesCountWeb-Details.png|center|thumb|500px|]]
The graph section allows you to overlay different metrics, and here you can see my heart rate compared with the estimate of Running Power provided by my [[Stryd]] sensor. The ability to overlay different metrics is a great tool for evaluating a workout. In addition to the usual metrics, and the [[Firstbeat]] estimated VO<sub>2</sub> & EPOC mentioned above there is also respiration rate, a rather unusual metric to see. This is also a [[Firstbeat]] estimated metric calculated from [[Heart Rate Variability]].
[[File:MovesCountWeb-Graph.png|center|thumb|500px|]]
An even more sophisticated option for visual analysis is the compare section the plots a scatter graph of 3 metrics. Below you can see my average heart rate against my speed, with the duration at that point given by the size. (This particular run is skewed by the time I spent changing shoes, so you see a large duration where I'm not moving.) This section of the website will probably only appeal to the geeks, but it's a really nice feature to see.
[[File:MovesCountWeb-Compare.png|center|thumb|500px|]]
Probably the coolest feature of the Moves Count website is one that makes it worth using for any runner, regardless of the type of watch they use. The heat map display shown below highlights where runners have recorded their work, giving a wonderful overview of the most popular running locations in any given area. The limitation of course is that it only represents data uploaded from Suunto devices, and there's not much data for less populated areas. Nonetheless, this is a great resource when you're looking for a new running route, or visiting a strange city.
 [[File:Suunto Heatmap.jpg|center|thumb|500px|]]
=Battery Life=
Suunto claim 18 hours of battery life, but I only got 17 hours in my testing. That's enough for most runners, but if you're into Ultramarathons, I'd suggest looking elsewhere. The Spartan can extend its battery life by reducing GPS accuracy, but even then, it's only 26 hours. 
=GPS Accuracy=
When the Spartan was released it had the worst [[GPS Accuracy]] of any watch I've tested. Subsequent firmware upgrades gradually improved the situation, and as of release 1.6.14 the accuracy is pretty good. (The actual GPS firmware is 5.7.10-P2.1-SNT.003.) My [[GPS Accuracy]] page has detailed, objective, statistical analysis of the Spartan and many other watches. I know that many readers prefer something a little less technical, so I've also included some rather more subjective visual representations below. You can see the improvement in the tracks with the updated firmware, as they are now closer together and have far fewer that wandered off on their own. You'll notice that the tracks form 2 distinct paths along the middle portion of the image, and it's not clear to me why this might be. My actual running path goes over the same points in both direction, and the split between the 2 sets of tracks does not appear to be directional. If you look at the lap markers you'll see that they are reasonably close together, which suggests both reasonable positional accuracy and fairly good responsiveness of the watch to the pressing of the lap button. The Spartan seems to have a few problems going under the bridge, which is not surprising, but seems to recover reasonably quickly. If you look at the color coding of the tracks, you'll see the middle, curved section has relatively good accuracy. I find this rather surprising, as this is a section that causes most watches the greatest issues. By comparison, the rightmost section with the sharp right angle turn does rather worse, and this is a section that most watches do okay on. If you look at the statistical analysis, you'll notice that the Spartan has relatively good trueness but poor precision compared with watches that have similar overall accuracy ratings. This means that compared with the watches of a similar accuracy rating, over a quarter of a mile distance (400 m) the Spartan is less likely to be correct, but over greater distances these errors are more likely to even out. These results are with GLONASS turned off, and I've seen dramatically worse results with it enabled.
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
|- valign="top"
|[[File:BridgeSuunto Spartan Ultra 1.6.14.jpg|none |thumb |x300px|This is the 1.6.14 version of the firmware. (This diagram has tracks color coded with green indicating good accuracy through to red indicating poor accuracy, and the lap markers as blue dots.)]]
|- valign="top"
|[[File:BridgeSuunto Spartan Ultra 1.4.6.jpg|none |thumb |x300px|This is the 1.4.6 version of the firmware. (This diagram has tracks color coded with green indicating good accuracy through to red indicating poor accuracy, and the lap markers as blue dots.)]]
|- valign="top"
|[[File:BridgeSuunto Spartan Ultra 1.2.4.jpg|none |thumb |x300px|For comparison, here's the earlier 1.2.4 Firmware.]]
|- valign="top"
|[[File:BridgeSuunto Ambit3 R.jpg|none |thumb |x300px|Here's how the [[Suunto Ambit3]]'s accuracy looks.]]
|- valign="top"
|}
==SGEE and Accuracy==
There are some suggestions online that syncing the Spartan before you run will improve GPS accuracy. The idea is that the sync will update the cache of satellite information (SGEE), which in turn will improve accuracy. This satellite information is a prediction of the GPS Ephemeris data, which gives information needed to use a satellite's signal for calculating the watch's position. Because it takes about 30 seconds to get a satellite's Ephemeris, having it preloaded reduces the time to get a usable location (Time To First Fix, TTFF.) This predicted Ephemeris data is not typically used to improve accuracy, but [http://www.telit.com/fileadmin/user_upload/Telit_Jupiter_SGEE_InstantFix_5_App_Note_r1.pdf a publication from Telit] suggests otherwise for the chipset used in the Spartan. The document is rather ambiguous, but I interpret it to mean that for the time between the watch getting an initial fix using the SGEE data and getting the true Ephemeris from the satellite the accuracy will be compromised. Given this should only be for a minute or so at the start of a run, this shouldn't have a practical impact. It's possible the situation may reoccur mid-run as satellites drop below the horizon and others rise up, as the watch will use SGEE data until the new satellites Ephemeris has been downloaded. To test how this worked in practice I did a few runs with the SGEE data expired (>7 days since the last sync) and I found that the GPS accuracy was not impaired. If anything, the accuracy might have been better without SGEE data, but I didn't collect enough data for statistical analysis. Of course, it's possible that slightly stale, but usable SGEE data might cause a problem. To test that I'd need to wait for a few days between syncing and gathering data, and repeat that for every run, which would take ages. 
=Heart Rate Variability=
The Spartan will record [[Heart Rate Variability]] (HRV) and export it in either FIT or XLS format. This can be processed in [https://runalyze.com Runalzye] or other similar software. There's no real-time display of HRV, but that functionality is pretty rare. 
[[File:Spartan HRV.jpg|center|thumb|700px|HRV from the Spartan in RUNALYZE]]
=Comparison Table=
{{:Best Running Watch-table}}