Joined
·
299 Posts
You may have seen a thread I posted a little while ago (Sarb033 Accuracy Disappointment). In that thread I mentioned that I received a new Sarb033 and I was worried about some accuracy issues with the new watch, and it's odd behavior I had been seeing. I have since spent some time closely monitoring this watch and I thought I would share what I've seen so far. Perhaps some members might find it interesting.
What Was My Monitoring Methodology?
1.) I hand wound the watch, 40-45 rotations of the crown, until feeling a slight change the action that I perceive as the over-wind protection or clutch kicking in.
2.) I set the clock's time as exact to the website Time.is as possible.
3.) I placed the watch in my storage case, dial up, in a 72 degree environment. The watch was not moved from this position.
4.) Every 4 hours (except when sleeping) the time on the watch was compared to the current time on the Time.is website and noted.
Note: A couple data points were estimated based on the the previous and following data points, for the purposes of sleeping and not being able to check the watch.
Why bother doing this?
When I purchase a new mechanical/automatic watch, I like to test it's accuracy in a simple static environment. Since a watch that has been worn can't be returned, this test gives me enough piece of mind to "unbox" the watch, resize the bracelet, and begin wearing it.
I am aware that the accuracy of the watch will be different when it's worn on the wrist, but for my piece of mind I want to find out if the watch performs reasonably well in a static and controlled environment first. Normally I am not this thorough, I just wind up the watch some and check it a couple times over the course of 24 hours. However, I noticed some wildly innacurate results with this Sarb033 initially, started to panic a little, and decided to test the watch more completely.
What were my findings?
During my first little test of the watch I was finding that the Sarb033 was wildly inaccurate. It was losing double digit seconds over the course of hours, not days. After that informal test I got much more thorough.
I found the following to be true about this Sarb033 while doing this test:
• It takes about 45 full rotations of the crown to get a complete charge on the 6R15c Movement.
• A complete charge lasted exactly 56 hours 28 minutes.
• The watch was extremely accurate over the course of the first 48 hours.
• The watch ranged between as much as +3 seconds faster than Time.is to -1 second slower than Time.is over the first 48 hours.
• Over the last 8 hours, at the end of the power reserve, the watch lost a lot of time.
• In those 8 hours the watch fell as far behind the Time.is official time as -26 seconds.
I now believe that during my initial testing of the watch, I was getting such wildly inaccurate results because I simply didn't charge up the watch enough. That said, I was always under the impression that a watch would typically speed up as the power reserve runs down. For whatever reason this 6R15c doesn't behave that way. I did see a youtube review where one user pointed out that his Sarb033 also lost a lot of time at the end of the power reserve.
I now wonder, is this typical of the 6R15c, but overlooked by the vast majority of users because they don't monitor their watch while it's power reserve is at the last 15%?
Or is this truly an anomaly with this particular example watch that I own?
I'm not sure...
The Data and Graph
What Was My Monitoring Methodology?
1.) I hand wound the watch, 40-45 rotations of the crown, until feeling a slight change the action that I perceive as the over-wind protection or clutch kicking in.
2.) I set the clock's time as exact to the website Time.is as possible.
3.) I placed the watch in my storage case, dial up, in a 72 degree environment. The watch was not moved from this position.
4.) Every 4 hours (except when sleeping) the time on the watch was compared to the current time on the Time.is website and noted.
Note: A couple data points were estimated based on the the previous and following data points, for the purposes of sleeping and not being able to check the watch.
Why bother doing this?
When I purchase a new mechanical/automatic watch, I like to test it's accuracy in a simple static environment. Since a watch that has been worn can't be returned, this test gives me enough piece of mind to "unbox" the watch, resize the bracelet, and begin wearing it.
I am aware that the accuracy of the watch will be different when it's worn on the wrist, but for my piece of mind I want to find out if the watch performs reasonably well in a static and controlled environment first. Normally I am not this thorough, I just wind up the watch some and check it a couple times over the course of 24 hours. However, I noticed some wildly innacurate results with this Sarb033 initially, started to panic a little, and decided to test the watch more completely.
What were my findings?
During my first little test of the watch I was finding that the Sarb033 was wildly inaccurate. It was losing double digit seconds over the course of hours, not days. After that informal test I got much more thorough.
I found the following to be true about this Sarb033 while doing this test:
• It takes about 45 full rotations of the crown to get a complete charge on the 6R15c Movement.
• A complete charge lasted exactly 56 hours 28 minutes.
• The watch was extremely accurate over the course of the first 48 hours.
• The watch ranged between as much as +3 seconds faster than Time.is to -1 second slower than Time.is over the first 48 hours.
• Over the last 8 hours, at the end of the power reserve, the watch lost a lot of time.
• In those 8 hours the watch fell as far behind the Time.is official time as -26 seconds.
I now believe that during my initial testing of the watch, I was getting such wildly inaccurate results because I simply didn't charge up the watch enough. That said, I was always under the impression that a watch would typically speed up as the power reserve runs down. For whatever reason this 6R15c doesn't behave that way. I did see a youtube review where one user pointed out that his Sarb033 also lost a lot of time at the end of the power reserve.
I now wonder, is this typical of the 6R15c, but overlooked by the vast majority of users because they don't monitor their watch while it's power reserve is at the last 15%?
Or is this truly an anomaly with this particular example watch that I own?
I'm not sure...
The Data and Graph
Code:
Text data that is represented on the graph below.
Duration (hours) Error (seconds)
---------------- ----------------
0 +0
4 +1
8 +2
12 +2
16 +3
20 +3
24 +3
28 +3
32 +3
36 +2
40 +1
44 +0
48 -1
52 -10
56 -26
