Global Bitcoin nodes by port number
295 port numbers with their respective number of global Bitcoin nodes as of Mon Dec 15 00:00:00 2025 UTC.
Window size: 1-day
| RANK | PORT NUMBER | NODES |
|---|---|---|
| 1 | 8333 | 64392 (89.35%) |
| 2 | 9333 | 2811 (3.90%) |
| 3 | 39388 | 1975 (2.74%) |
| 4 | 8334 | 1736 (2.41%) |
| 5 | 12333 | 139 (0.19%) |
| 6 | 8332 | 116 (0.16%) |
| 7 | 8303 | 64 (0.09%) |
| 8 | 8335 | 60 (0.08%) |
| 8 | 18333 | 60 (0.08%) |
| 9 | 1337 | 39 (0.05%) |
| 10 | 7335 | 35 (0.05%) |
| 11 | 8433 | 31 (0.04%) |
| 12 | 8340 | 27 (0.04%) |
| 13 | 42069 | 17 (0.02%) |
| 14 | 8555 | 16 (0.02%) |
| 15 | 7333 | 15 (0.02%) |
| 16 | 20008 | 14 (0.02%) |
| 17 | 10001 | 12 (0.02%) |
| 17 | 30241 | 12 (0.02%) |
| 18 | 8336 | 11 (0.02%) |
| 19 | 8330 | 10 (0.01%) |
| 19 | 18444 | 10 (0.01%) |
| 20 | 8331 | 8 (0.01%) |
| 21 | 5001 | 7 (0.01%) |
| 21 | 8338 | 7 (0.01%) |
This page reports the estimated size of the Bitcoin peer-to-peer network including both reachable and unreachable nodes, i.e. global nodes. Unlike the low churn rate estimation method for reachable nodes (see the latest snapshot here), the method for this report can only provide a rough estimation and does not filter out potentially spurious nodes that may be gossiped by non-standard/spam/malicious peers.
Bitnodes crawler captures these nodes from the addr messages returned by all the reachable nodes. Each snapshot or data point in this report represents a rolling window. A snapshot with window size of 1 day will include all nodes by IP addresses with timestamps less than 1 day old. The timestamp for a node here refers to the time when its peer last connects to it. If you turn on your Bitcoin node for only a few minutes anytime during the last 24 hours, it will be included in the latest snapshot with a window size of 1 day.
Multiple nodes from the same IP address, but different port numbers are counted as one node in this report. A larger window size may increase the likelihood of the same node being counted more than once due to, e.g., IP lease renewal.
A Bitcoin node may be unreachable for several reasons. It may be configured by the operator to only attempt to make outgoing connections or it may be located behind corporate/ISP firewalls or NAT. A node could also become temporarily unreachable if it has hit its maximum allowed connections or if it is in the process of syncing up to the latest blocks. As it is impossible to connect to an unreachable node directly, we cannot reliably confirm the true existence of an unreachable node, hence the rough estimation.