My 3rd Midnattsloppet

Last Saturday I run my third Midnattsloppet in 50m52s (10 km). It was the fastest I have ever run I guess and since last week I did not feel very well I'm very satisfied. I had some problems after 7 km where my stomach was giving me some problems but after resting for about a minute I could start run again.

If I use the results of the previous years I can see that I've been improving my running quite a lot:

  • 2008 50.52



  • 2007 53.05



  • 2006 57:02


I think I can now start practising for the Lidingöloppet, which is 30 km and much harder. But at least I feel well

Comments

  1. Michael14 June 2009 at 13:10

    Hey Roberto,
    I see you ran the midnattsloppet for the 3rd time last year! Well done with your progressive times! I ran it in stockholm in 2007 in a time of 56.23...not bad considering I was still smoking back then and only trained for two weeks beforehand! Gee, I cant believe I actually smoked.
    I hope to make it back to Sweden this year to run.I havent entered yet, but I am running in training as if I am entered.
    I have a question and was wondering if you knew the answer since you have been in a few races. I would be aiming to run under 50 min this time, and should have been in group 2 with that time. But since I have left it late, all the positions have gone in group 2, right down to group 6. Could I enter with group 7, then start with the runners from group 2? Would my time piece work when I crossed the finish line to commence? I was just wondering cause I didnt want to start way back in group 7 if I do actually get to stockholm on the 15th of August.
    Hope youre there this year, I may see you!
    Michael from Cairns Australia

    ReplyDelete

Post a Comment

Popular posts from this blog

Home Assistant in Docker on MacOs BigSur

  Install brew. Follow instructions on https://brew.sh/ Install virtualbox # brew install virtualbox Install docker-machine # brew install docker-machine # brew services start docker-machine If you want the machine to run at boot (rather than at login) Move your launchd configuration file homebrew.mxcl.docker-machine.plist from $USER/Library/LaunchAgents to /Library/LaunchDaemons Add a user directive:  <key>UserName</key> <string>robcos</string> Make sure the permissions are right: # sudo chmod root.wheel homebrew.mxcl.docker-machine.plist Install docker # brew install docker Create a virtual machine # docker-machine create --driver=virtualbox default Setup docker environment (you will need this every time you open a new shell) # eval $(docker-machine env default) Setup your “default” virtualbox to forward any relevant port.  Settings -> Network -> Adapter 1 -> Nat -> Advanced In my case I forward 1880 for NodeRed, 8123 for HomeAssistan...
Read more

The little yellow book of vaccinations

Image
I have almost filled my yellow book with vaccinations. You get it when you contact NHS and make an appointment with your closest travel clinic. I went to my usual surgery Sterndale in Hammersmith. The nurse recommended to get Hepatitis A and B, Typhoid, Rabies and the compulsory Yellow Fever. Some of them require more than one shot so make sure to start your treatment at least 3 weeks before you leave. I am also going to get an anti malaria treatment but for that I need another appointment. The injection are almost harmless so don't be scared. Be scared of the bill though as some of those vaccines are not free and cost up to 40£ per short. And yes, you can also use private clinics as Nomad (STA Travel) but it will cost you more.
Read more

ReadyNas NV+ and rsync

Setting up an account to backup a windows machine to my Nas I discovered an issue with the rsync setup. I first enabled the rsync protocol in the readynas admin interface. I then added a new user account and when I was testing I got the following error: rsync -av myidr/ newuser@mynas: newuser@mynas's password: Connection closed by 192.168.1.100 rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: unexplained error (code 255) at /SourceCache/rsync/rsync-35.2/rsync/io.c(452) [sender=2.6.9] I tracked down the problem to not having a ssh key on the nas for the new user: su - newuser Password: newuser@mynas:~$ ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/c/home/newuser/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in . Your public key has been saved in .pub. The key fingerprint is: c1:25:12:5b:21:18:31:23:73:58:45:99:2c:0b:0e:7c newuser...
Read more