Found 7 Confirmed VMODEM Nodes
| Node Address | Hostname | Location | Last Tested | Actions |
|---|---|---|---|---|
| 2:5025/2 | f2.n5025.ru |
Voronezh, RU
Informsvyaz-Chernozemye |
2026-08-26 14:13 | |
| 2:423/81 | fido.bajer.cz |
Brno, CZ
Vodafone Czech Republic |
2026-08-26 02:19 | |
| 2:221/360 | f360.n221.z2.fidonet.fi |
Vihti, FI
DNA Oyj |
2026-08-23 17:44 | |
| 1:342/806 | xanadubbs.ca |
Edmonton, CA
Shaw Communications |
2026-08-23 13:34 | |
| 2:334/403 | f403.n334.z2.binkp.net |
Sciacca, IT
Tiscali Italia SpA |
2026-08-23 00:55 | |
| 2:2432/394 | ftn.owlserver.de |
Löhne, DE
EWE TEL GmbH |
2026-08-22 02:02 | |
| 2:371/52 | bbs.roonsbbs.hu |
Budapest, HU
Magyar Telekom |
2026-08-18 15:52 |
Note: This report shows nodes whose announced IVM port was confirmed over the last 30 days to run Ray Gwinn's Virtual Modem Protocol (VMP) — the protocol the IVM flag actually stands for. VMODEM provides virtual modem emulation so legacy mailer software can place FidoNet calls over TCP/IP.
Why the list is short: most IVM-flagged ports do not run VMODEM. Probing them commonly finds an EMSI mailer over telnet or raw TCP, binkd, or a plain telnet login prompt instead. Those ports are reachable, but they are not VMODEM, so they are excluded here — see each node's test history for what was actually found.
Confirmed is not the same as called: a node qualifies once it answers as a VMODEM. Placing a real VMP call rings the remote sysop's mailer and needs a reverse data channel back to us, so it is not done on every cycle. A node's test history shows whether a call was ever put through.
Note about Location: The "Location" column shows the geographic location determined from the node's IP address (via GeoIP lookup), not the location specified in the nodelist. This represents the actual physical location where the node's server is hosted.