4.70
4d ago
Jun 12, 2016(9y)
Jun 12, 2026(13d)
Combat
Kills344
Losses108
Efficiency76%
ISK
Destroyed169.33b
Lost14.01b
ISK Eff.92%
Solo
Solo Kills34
Solo Ratio10%
Final Blows99
Points394
Other
NPC Losses24
NPC Loss Ratio22%
Avg Kills/Day0.09
ActivityHigh
Caldari
Achura
4.70
Last Active
4d ago
Birthday
Jun 12, 2016 (9 years old)
Next Birthday
Jun 12, 2026 (13 days)
Combat
Kills344
Losses108
Efficiency76%
Danger Ratio78%
ISK
Destroyed169.33b
Lost14.01b
ISK Efficiency92%
Balance+155.31b
Solo
Solo Kills34
Solo Ratio10%
Final Blows99
Points394
Other
NPC Losses24
NPC Loss Ratio22%
Avg Kills/Day0.09
ActivityHigh
Bio
V∇⊼⋖⊿Λ
⋜⊴Γ⋖⊿⊴
Δ7⊼7Δ7
7⋖L⊿≧7
⊼⋖7⋚⋜Λ
⊼⋖ ⊴⊼⋜⋖V⊴
⊽⊴⋖Γ ⊿Γ⋚ΛΓ⋖⋈⊴⋚⊴
⋖≧⊽∇⋖Δ ∇Γ∇⋖Δ∇LΛΓ⋚
⊿⊼⋖⋜⊽⊴ Zorya Triglav Is My Sugar Mommy
⊼⋖Γ⊴≶⊿ LLΛΓ⋖7⋚⋖Δ7⊽ΔΛ7⋜Λ⋖V⊴⊼⋜⊽∇⋖
⊼Λ⋚⋜⋖⋈ 7Δ⋖⊼Λ⋚⋜⋖ΔL⊿V⊴⊼⋖⋈ΛΓ7⋖⋜⊿Γ⋖
⊼ΛΛΓΛ⊽ ⊿⋚⋜⊴Γ⋖
⊽⊴≧⊴⊽7 ∇⋖LΛΔ⊴
⊽⋚⊿⋖⊿⊽
7⊼⋖≧⊽∇
≧⊴⋖⊴
drink bepis
The missile knows where it is at all times. It knows this because it knows where it isn't. By subtracting where it is from where it isn't, or where it isn't from where it is - whichever is greater - it obtains a difference or deviation. The guidance subsystem uses deviations to generate corrective commands to drive the missile from a position where it is to a position where it isn't, and arriving at a position that it wasn't, it now is. Consequently, the position where it is is now the position that it wasn't, and if follows that the position that it was is now the position that it isn't. In the event that the position that the position that it is in is not the position that it wasn't, the system has acquired a variation. The variation being the difference between where the missile is and where it wasn't. If variation is considered to be a significant factor, it too may be corrected by the GEA. However, the missile must also know where it was. The missile guidance computer scenario works as follows: Because a variation has modified some of the information that the missile has obtained, it is not sure just where it is. However, it is sure where it isn't, within reason, and it know where it was. It now subtracts where it should be from where it wasn't, or vice versa. And by differentiating this from the algebraic sum of where it shouldn't be and where it was, it is able to obtain the deviation and its variation, which is called error.
⋜⊴Γ⋖⊿⊴
Δ7⊼7Δ7
7⋖L⊿≧7
⊼⋖7⋚⋜Λ
⊼⋖ ⊴⊼⋜⋖V⊴
⊽⊴⋖Γ ⊿Γ⋚ΛΓ⋖⋈⊴⋚⊴
⋖≧⊽∇⋖Δ ∇Γ∇⋖Δ∇LΛΓ⋚
⊿⊼⋖⋜⊽⊴ Zorya Triglav Is My Sugar Mommy
⊼⋖Γ⊴≶⊿ LLΛΓ⋖7⋚⋖Δ7⊽ΔΛ7⋜Λ⋖V⊴⊼⋜⊽∇⋖
⊼Λ⋚⋜⋖⋈ 7Δ⋖⊼Λ⋚⋜⋖ΔL⊿V⊴⊼⋖⋈ΛΓ7⋖⋜⊿Γ⋖
⊼ΛΛΓΛ⊽ ⊿⋚⋜⊴Γ⋖
⊽⊴≧⊴⊽7 ∇⋖LΛΔ⊴
⊽⋚⊿⋖⊿⊽
7⊼⋖≧⊽∇
≧⊴⋖⊴
drink bepis
The missile knows where it is at all times. It knows this because it knows where it isn't. By subtracting where it is from where it isn't, or where it isn't from where it is - whichever is greater - it obtains a difference or deviation. The guidance subsystem uses deviations to generate corrective commands to drive the missile from a position where it is to a position where it isn't, and arriving at a position that it wasn't, it now is. Consequently, the position where it is is now the position that it wasn't, and if follows that the position that it was is now the position that it isn't. In the event that the position that the position that it is in is not the position that it wasn't, the system has acquired a variation. The variation being the difference between where the missile is and where it wasn't. If variation is considered to be a significant factor, it too may be corrected by the GEA. However, the missile must also know where it was. The missile guidance computer scenario works as follows: Because a variation has modified some of the information that the missile has obtained, it is not sure just where it is. However, it is sure where it isn't, within reason, and it know where it was. It now subtracts where it should be from where it wasn't, or vice versa. And by differentiating this from the algebraic sum of where it shouldn't be and where it was, it is able to obtain the deviation and its variation, which is called error.
Dashboard
Stats
Kills57
Losses14
Efficiency80%
ISK Destroyed21.80b
ISK Lost1.08b
ISK Efficiency95%
Solo Kills4
Solo Losses7
NPC Losses1
Blob Factor20.47
Active TimezoneEUTZ
Final Blows9
Points107
Activity Heat Map (EVE Time)
00
6
01
1
02
1
03
0
04
5
05
2
06
0
07
0
08
0
09
0
10
0
11
0
12
0
13
0
14
1
15
5
16
1
17
6
18
12
19
5
20
0
21
1
22
1
23
10
Intel Profile
PlaystyleFleet (57 kills)
Solo 4% Small 25% Mid 26% Fleet 37% Blob 9%
Avg Fleet: 20.5 Logi Pilot Bait (2x)
Typically Loses
Targets (Alliances)
Top Fleet Partners
