Clear to jump captain. As long as you haven't double jumped recently.

http://wiki.eveonline.com/en/wiki/Wormholes#Polarization

"If you jump the same wormhole twice within 5 minutes, you are polarised and cannot jump that wormhole any more until 5 minutes after the initial jump."

Thanks for the quick answer. :)
So the only way to stop someone from escaping trough a WH would be to bump them out of range to enter the WH or hinder them in getting in range with webs?

5 minutes per side as well. This means in rare cases you can be clear on one side of a wormhole but when you try to jump back you'll have a timer on the other side.

Example: you jump through a B274 and wait 3 minutes. Then you jump back through the K162 (starting a new timer) and wait 2 minutes. Now your original 5 minute timer is clear, so you jump back through the B274, but you are still timered approximately 3 minutes on the K162 side.

1) -> B274 (B274 timer started)
2) 3 minutes
3) -> K162 back into the wormhole (K162 timer started)
4) 2 minutes
5) -> B274 (B274 new 5 min timer)
6) -|> try to jump K162 again, but ~3 minutes remaining.

Svo.

Polarity timer is 4 minutes.

I thought 5 minutes as well.... but then I'm wrong a lot.

youre not wrong, it is 5min.
the 4min number comes from when you had 2 30s session change timers to wait out too.

go find a wh.
jump through it.
jump back immediately.
try to jump back again.
your timer will be 4m30s odd. certainly more than 4min.

youre not wrong, it is 5min.
the 4min number comes from when you had 2 30s session change timers to wait out too.

Thanks for the quick answer. :)
So the only way to stop someone from escaping trough a WH would be to bump them out of range to enter the WH or hinder them in getting in range with webs?

It's been 4 minutes for the longest time.

Also the session change timer on WH's isn't 30 seconds.

your timer will be 4m30s odd. certainly more than 4min.

While the rest of you were armchair quarterbacking, I was out and busily testing and recording timers on different types of wormhole connections:

H296 (C5->C5): 5 minutes
E175 (C5>C4): 5 minutes
X877 (C5>C4): 5 minutes
N766 (C4>C2): 5 minutes

Each link above connects to a screenshot showing the timer on the third-jump polarization message. As Jack Miton has stated, there are an additional 20 seconds for the session timers, plus approach-time and general syncing.

SCIENCE, BITCHES!!!

EDIT:
ooh pity I just noticed the last picture has 4m28s . Pretty stupid amount for the timer if they don't use an 8bit counter.

It's...it's almost like...they can program whatever number they actually want.

no way, how?

Seriously though, for optimization purposes, with that timer (~258 seconds) it would be wise for them to use an 8 bit counter (e.g. unsigned char = 8 bit counter -> 0-255) because it reduces their data foot print for WH timers to be 2-4 times smaller (on 32 bit software a short = 16 bit and an int = 32 bit). For the amount of data that the servers need to handle I would consider that every bit of data reduction would be a nice thing to have, but that of course doesn't mean CCP thinks of such things.

It's 300 seconds. 5 Minutes.

What you're talking about is optimizing the tiniest bit of data usage on the whole server. My KEYBOARD runs a 5 minute timer without lag.

But to make it clear to all of you that are aggressively set to the 5 minute timer, I'm not stating that CCP uses an 8 bit counter to give you a timer of ~4m26s + 2*10s + couple of seconds delay. To me it merely looks like it, but without seeing some code or having CCP state that's how they do it I can never state it as fact. For all I care they use an 64 bit long and throw around unnecessary data.