Station info - [map view · info · telemetry · weather · raw · status · beacons · messages · bulletins · browse · moving · my account]
Callsign, ship name or locator: Clear       
It is possible to search using wildcards (*?) after a prefix. Example: OH*
APRS station K5DAT-10 - show graphs Bookmark and Share
Map loading...
Comment: APRSIS32-Linux-Wine
Last status: Lee in Leesburg
Location: 39°07.01' N 77°33.30' W - locator FM19FC38JA - show map - static map
0.5 miles East bearing 80° from Leesburg, Loudoun County, Virginia, United States [?]
7.7 miles West bearing 255° from Poolesville, Montgomery County, Maryland, United States
31.8 miles Northwest bearing 299° from Washington, Washington, D.C., United States
51.8 miles West bearing 257° from Baltimore, City of Baltimore, Maryland, United States
Last position: 2012-05-23 04:53:55 UTC (1m19s ago)
2012-05-23 00:53:55 EDT local time at Leesburg, United States [?]
Last telemetry: 2012-04-14 19:55:14 UTC (38d 9h ago) – show telemetry
Avg 10m: 0.075 Rx Erlang, Avg 10m: 0.001 Tx Erlang, RxPkts: 73 count/10m, IGateDropRx: 1 count/10m, TxPkts: 0 count/10m
Device: KJ4ERJ: APRSIS32 version 09 (software, Windows)
Last path: K5DAT-10>APWW09 via TCPIP*,qAC,SEVENTH
Positions stored: 290
Packet rate: 888 seconds between packets on average during 44412 seconds.
Other SSIDs: K5DAT K5DAT-1 K5DAT-11 K5DAT-12 K5DAT-15 K5DAT-2 K5DAT-3 K5DAT-4 K5DAT-5 K5DAT-7 K5DAT-9
APRS igate – Statistics for 2012-05:
Stations heard directly: 42 on radio path – show map
Last heard a station directly: 2012-05-23 04:54:49 UTC (25s ago)
Normal receiver range estimate: 12 miles (Updated: 2012-05-23 02:53:47 UTC)
Position packets heard directly: 8002 on radio path
Position packets sent to APRS-IS: 17727 – show map
Stations near current position of K5DAT-10 - show more
callsign distance last heard - UTC      callsign distance last heard - UTC
K5DAT0.0 yards 0°2012-05-23 04:29:39 K5DAT-20.0 yards 0°2012-05-21 04:49:10
K5DAT-931.1 yards 90°2012-05-21 23:52:43 K5DAT-12189.6 yards 96°2012-05-02 22:32:44
CW5376294.9 yards 345°2012-05-23 04:46:03 K6BFA-90.6 miles 251°2012-05-14 16:30:50
KE4IHG-71.0 miles 148°2012-05-22 19:51:04 KI4IEO-21.1 miles 61°2012-05-23 04:54:49
KG4PES-11.3 miles 200°2012-05-21 15:22:53 KE4FYL-11.4 miles 268°2012-05-23 04:53:50
W8MTL-71.8 miles 256°2012-05-22 22:23:03 KJ4GYH-41.9 miles 224°2012-05-20 19:39:20
DW92091.9 miles 282°2012-05-23 04:38:20 N4PD-92.1 miles 232°2012-05-21 00:18:17
DW81723.1 miles 9°2012-05-23 04:47:06 KI4HS-93.2 miles 103°2012-05-20 02:17:24
AJ4TJ-73.6 miles 190°2012-05-20 20:47:20 DW70435.2 miles 141°2012-05-23 04:50:29
KE4S-45.8 miles 204°2012-05-23 03:51:17 KJ4VZN-16.2 miles 143°2012-05-08 06:03:27
Stations which heard K5DAT-10 directly on radio –
callsign pkts first heard - UTC last heard longest (tx => rx) longest at - UTC
KV3B-1 51 2012-05-14 01:38:06 2012-05-23 03:56:13 FM19FC > FM19JE 17.2 miles 74° 2012-05-23 03:56:13

Only position packets which were originated by the station are shown here. The range statistics show some extra long hops, because some digipeaters do not correctly add themselves to the digipeater path. Please check the raw packets.
Stations heard directly by K5DAT-10
callsign pkts first heard - UTC last heard longest (rx => tx) longest at - UTC
KG6DNI 31 2012-05-02 22:44:50 2012-05-22 22:33:45 FM19FB > FM19FC 3.2 miles 189° 2012-05-10 10:50:10
W4IFI-2 3 2012-05-01 20:00:52 2012-05-01 21:38:39 FM19EC > FM19FC 3.2 miles 225° 2012-05-01 20:00:52
KE4S-4 2 2012-05-12 19:46:39 2012-05-14 16:46:43 FM19EA > FM19FC 5.8 miles 204° 2012-05-14 16:46:43
KE5APC-9 30 2012-05-02 12:58:53 2012-05-21 12:59:19 FM19FB > FM19FC 3.6 miles 190° 2012-05-16 23:15:15
KE4S-9 32 2012-05-01 17:54:43 2012-05-20 15:30:56 FM19EC > FM19FC 2.8 miles 219° 2012-05-20 15:30:56
N9LOE 47 2012-05-19 21:38:25 2012-05-19 23:14:26 FM19FC > FM19FC 2.0 miles 223° 2012-05-19 21:44:30
N2IGU-5 4 2012-05-14 23:18:54 2012-05-14 23:24:59 FM19FB > FM19FC 2.7 miles 194° 2012-05-14 23:24:59
AI1V-9 3 2012-05-19 14:36:08 2012-05-19 14:38:46 FM19FC > FM19FC 1.9 miles 197° 2012-05-19 14:38:46
KE4FYL-1 2756 2012-05-01 00:22:14 2012-05-23 04:53:50 FM19FC > FM19FC 1.4 miles 268° 2012-05-23 04:53:50
W8MTL-7 15 2012-05-01 22:08:48 2012-05-21 22:03:31 FM19FC > FM19FC 3.4 miles 132° 2012-05-04 17:09:22
K8WDX-7 44 2012-05-01 10:16:52 2012-05-08 21:48:28 FM19FB > FM19FC 3.6 miles 131° 2012-05-02 10:30:09
KG4LAA-15 2 2012-05-02 17:21:42 2012-05-05 17:36:53 FM18GW > FM19FC 12.6 miles 151° 2012-05-02 17:21:42
KS1G-4 14 2012-05-12 13:06:43 2012-05-12 16:35:02 FM19FC > FM19FC 1.6 miles 198° 2012-05-12 13:06:43
KI4IEO-2 2204 2012-05-01 00:04:28 2012-05-23 04:54:49 FM19FC > FM19FC 1.1 miles 61° 2012-05-23 04:54:49
KA2ZEV-9 1 2012-05-09 23:08:24 2012-05-09 23:08:24 FM18HX > FM19FC 14.9 miles 134° 2012-05-09 23:08:24
KA2ZEV-8 2 2012-05-06 23:29:10 2012-05-06 23:32:07 FM19FC > FM19FC 1.4 miles 223° 2012-05-06 23:29:10
W3CUM-9 6 2012-05-19 22:25:12 2012-05-19 22:32:57 FM19FC > FM19FC 3.3 miles 132° 2012-05-19 22:25:12
WA0DYJ-7 7 2012-05-16 12:27:15 2012-05-16 12:37:33 FM19FC > FM19FC 1.9 miles 223° 2012-05-16 12:27:15
K4USS-8 15 2012-05-09 17:52:18 2012-05-09 18:27:18 FM19ED > FM19FC 2.2 miles 301° 2012-05-09 18:27:18
KI4TXP-9 49 2012-05-04 14:53:02 2012-05-19 17:24:08 FM19FF > FM19FC 7.2 miles 2° 2012-05-04 14:53:02
K6BFA-9 6 2012-05-14 16:22:16 2012-05-14 16:30:50 FM19FC > FM19FC 0.9 miles 228° 2012-05-14 16:29:18
N4PD-9 21 2012-05-12 23:57:01 2012-05-21 00:18:17 FM19EC > FM19FC 3.2 miles 225° 2012-05-13 19:41:56
N4TCW 17 2012-05-17 11:51:06 2012-05-21 18:01:56 FM19FC > FM19FC 1.7 miles 138° 2012-05-21 17:53:19
KE4IHG-7 9 2012-05-02 19:57:59 2012-05-22 19:51:04 FM19FC > FM19FC 1.1 miles 144° 2012-05-15 19:51:11
KV3B-1 2423 2012-05-01 00:36:21 2012-05-23 04:22:37 FM19JE > FM19FC 17.2 miles 74° 2012-05-23 04:22:37
W3RST-8 45 2012-05-01 10:46:33 2012-05-16 16:45:59 FM19FB > FM19FC 2.7 miles 178° 2012-05-01 10:52:49
KG4UPR-9 11 2012-05-12 09:30:17 2012-05-19 14:33:00 FM19EC > FM19FC 1.6 miles 262° 2012-05-12 09:33:42
KJ4VOV-9 1 2012-05-05 03:08:28 2012-05-05 03:08:28 FM18GX > FM19FC 12.3 miles 150° 2012-05-05 03:08:28
W4CLK-9 2 2012-05-15 14:05:01 2012-05-15 14:32:23 FM19FC > FM19FC 0.9 miles 150° 2012-05-15 14:05:01
W4SDM-1 3 2012-05-19 22:40:51 2012-05-19 22:49:08 FM19FB > FM19FC 3.4 miles 204° 2012-05-19 22:49:08
KB3VSQ-7 6 2012-05-22 13:58:28 2012-05-22 20:06:41 FM19FC > FM19FC 2.3 miles 196° 2012-05-22 20:02:46
KG4PES-1 1 2012-05-19 15:05:56 2012-05-19 15:05:56 FM19FC > FM19FC 1.0 miles 117° 2012-05-19 15:05:56
KE5APC-10 8 2012-05-12 16:01:30 2012-05-12 16:11:41 FM19FC > FM19FC 0.7 miles 160° 2012-05-12 16:10:03
WB5ODJ-8 2 2012-05-01 03:15:55 2012-05-01 03:16:55 FM19FC > FM19FC 1.2 miles 172° 2012-05-01 03:16:55
AJ4TJ-7 5 2012-05-20 17:21:07 2012-05-20 20:42:29 FM19FC > FM19FC 1.6 miles 199° 2012-05-20 20:42:29
KB3LVU-9 3 2012-05-16 21:58:52 2012-05-16 22:01:03 FM19FC > FM19FC 2.1 miles 205° 2012-05-16 22:01:03
K5DAT-12 2 2012-05-02 22:09:48 2012-05-02 22:31:58 FM19FC > FM19FC 1.5 miles 151° 2012-05-02 22:09:48
KJ4GYH-4 36 2012-05-13 17:33:29 2012-05-20 19:37:02 FM19EC > FM19FC 2.0 miles 236° 2012-05-17 11:21:57
KD4WTC-15 1 2012-05-12 13:42:24 2012-05-12 13:42:24 FM19FC > FM19FC 1.2 miles 195° 2012-05-12 13:42:24
K5DAT-9 119 2012-05-02 02:29:54 2012-05-21 23:50:51 JM09AC > FM19FC 4014.8 miles 63° 2012-05-21 23:44:51
KG4JAO-9 2 2012-05-16 16:34:25 2012-05-16 16:37:27 FM19FC > FM19FC 1.4 miles 217° 2012-05-16 16:34:25
KB3NVF 12 2012-05-22 09:00:31 2012-05-22 18:37:50 FM19FF > FM19FC 6.7 miles 9° 2012-05-22 18:37:50

Only stations from which a position packet has been heard are shown here. The range statistics show some extra long hops, because some digipeaters do not correctly add themselves to the digipeater path. Please check the raw packets.
About this site
This page shows real-time information collected from the Automatic Position Reporting System Internet network (APRS-IS). APRS is used by amateur (ham) radio operators to transmit real-time position information, weather data, telemetry and messages over the radio. A vehicle equipped with a GPS receiver, a VHF transmitter or HF transceiver and a small computer device called a tracker transmits it's location, speed and course in a small data packet, which is then received by a nearby iGate receiving site which forwards the packet on the Internet. Systems connected to the Internet can send information on the APRS-IS without a radio transmitter, or collect and display information transmitted anywhere in the world.
User guide · FAQ · Blog · Discussion group · Linking to aprs.fi · AIS sites · Service status · Database statistics · Advertising on aprs.fi · Technical details · API · Change log · Planned changes · Credits and thanks · Terms Of Service · Maatana