First of all, in my case, I was planning to « tweet while running » and « tweak while running », so of course my pacing had to be more relaxed than just running.
Although the Tokyo Marathon has a relaxed time limit for those who want to run while having fun, I feel that the gate and time limit are surprisingly strict for those who want to « play » in various ways.
I had set my target pace in advance, but the race turned out to be more difficult than I had expected due to the delay in the start time, the timing of the restroom, and the lack of consideration in these areas. The rain also had an effect, though. It was also my first marathon.
But this time, I can think about the allocation based on this experience, and above all, I understand how painful it is to run 42.195km, and I can predict to some extent where I will suffer and where my legs will hurt.
I made this allocation in advance based on that experience.
Basically, each 5km gate is set 30 minutes before the time limit.
The start time is expected to be around 9:25 a.m. based on previous experience (Tokyo Marathon starts at 9:10 a.m.)
The split time of 5km was set to « 40 minutes » in consideration of walking at the timing of water supply, stopping occasionally to take photos, etc.
Midway point, Ginza (22km), Nihonbashi (23km), Asakusa Kaminarimon (27km), turn back Ginza (34km), Tsukuda Ohashi (36km), after Toyosu (after 38km), walk 1km before and after.
considered. In addition to that.
Passed the 20km point (Shimbashi) around 12:00
Passed the 32km point (Kayabacho) around 14:00
I put this in my head.
And here are the results of my run on the day.
Date:2011/02/27
ナンバー(Bib number)：43380
種目(Category)：マラソン男子
地点名
Point
スプリット (ネットタイム)
Split (Net Time)
ラップ
Lap
通過時間
Time
5km
00:57:32 (0:37:19)
0:37:19
10:07:32
10km
01:33:28 (1:13:15)
0:35:56
10:43:28
15km
02:10:08 (1:49:55)
0:36:40
11:20:08
20km
02:53:56 (2:33:43)
0:43:48
12:03:56
25km
03:40:46 (3:20:33)
0:46:50
12:50:46
30km
04:28:43 (4:08:30)
0:47:57
13:38:43
35km
05:18:00 (4:57:47)
0:49:17
14:28:00
40km
06:14:53 (5:54:40)
0:56:53
15:24:53
Finish
06:48:51 (6:28:38)
0:33:58
15:58:51
I think I ran almost exactly as planned, or maybe too well as planned. The pace was relaxed, but I walked, took bathroom breaks, and most importantly, took photos, tweeted, and tweeted. I’m afraid I’m praising myself, but I’m really impressed with how well I did.
If you ran without any tweets or tweets at all…
As I mentioned above, the Tokyo Marathon was able to proceed as planned, but if I had run without any tweets or tweaking, what would have been my time and pace?
To sum it up, I’d imagine it’s « 5 hours to 5 hours and 30 minutes ».
In fact, I thought I had trained myself to be able to run that fast. I had set myself a « target time », albeit a tentative one.
You have to be able to run a certain way to tweet & tweak.
However, my actual time was 6 hours and 30 minutes, which means I was just under the time limit.
So, after stating the hypothetical target time above, I think it’s not so meaningless to talk about it here, and in fact, if you can’t imagine it, you can’t do the Tweet & Tweakathon.
The reason I ask is because I believe that if you don’t know this « true strength » of yours, you won’t be able to set a conscious pacing for your tweets and tweets.
So when I trained, I set a goal of training myself to be able to run a full marathon in about 5 hours to 5 hours and 30 minutes.
In fact, during the Tokyo Marathon, I ran next to Joseph, who became famous for his iRun, several times, and I think he is a very skilled runner.
Even though I’m tall and have a very long stride, I think I’m very fast when I run normally, I think I can break 4 hours.
Preparing tweets and tweets in advance to reduce energy consumption on the day
To look at it differently, you can think of it as needing to be able to run at least this fast in order to be able to stop and tweet, take pictures, and tweak along the way.
Stopping to tweet or tweak during a full marathon while worrying about the battery or mobile WiFi signal is more physically and mentally draining than expected. In that sense, if you don’t carefully prepare your mobile devices beforehand, it will cause you to lose even more energy on the day.
In particular, the most important thing to me was real-time location information transmission. I thought this was the best part of the marathon while twittering more.
We dealt with this by carefully rehearsing the sending of current location information using Ima Koko Now, registering a venue in advance using foursquare, and registering a 30-minute tweet reservation using HootSuite.
Lastly: I was able to run the remaining 17km thanks to real-time information dissemination!
(Sorry for the delay in updating due to the earthquake)
Thanks to all of you, I was able to participate in this event for the second time since the third one, and I was able to finish the race despite the high ratio of participants.
I think I was able to run about 25km on my own, and the remaining 17km was thanks to everyone who supported me, especially on twitter.
In fact, this is the biggest reason why I’ve been so particular about sending out real-time information. To be honest, I thought I could never run 42.195km on my own. It’s only when people pay attention to me and cheer me on that I can run the remaining 17km.
And I realized again that this is really a powerful thing.
