Channel
VINTAGE STATION
@StationVintage
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
19,795subscribers
-402 since we began measuring on 6 September 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1002248668758 |
|---|---|
| Type | Channel |
| Username | @StationVintage |
| Created | Between 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 24 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 24 October 2026 |
| On Telegram | t.me/StationVintage |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Oct 2026, 13:56 | 19,795 | -7 |
| 23 Oct 2026, 14:15 | 19,802 | -6 |
| 22 Oct 2026, 17:45 | 19,808 | -7 |
| 21 Oct 2026, 14:57 | 19,815 | -7 |
| 20 Oct 2026, 11:55 | 19,822 | -4 |
| 19 Oct 2026, 14:15 | 19,826 | -10 |
| 18 Oct 2026, 13:56 | 19,836 | -4 |
| 17 Oct 2026, 16:38 | 19,840 | -3 |
| 16 Oct 2026, 18:46 | 19,843 | -8 |
| 15 Oct 2026, 21:17 | 19,851 | -7 |
| 14 Oct 2026, 22:47 | 19,858 | -10 |
| 13 Oct 2026, 13:28 | 19,868 | -46 |
| 9 Oct 2026, 14:01 | 19,914 | -43 |
| 5 Oct 2026, 03:16 | 19,957 | -64 |
| 28 Sept 2026, 07:00 | 20,021 | -88 |
| 17 Sept 2026, 16:42 | 20,109 | -10 |
| 15 Sept 2026, 16:18 | 20,119 | -15 |
| 13 Sept 2026, 20:58 | 20,134 | -22 |
| 12 Sept 2026, 05:20 | 20,156 | -15 |
| 10 Sept 2026, 01:58 | 20,171 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@tsetmc_1330 · 5,734#1
@lmscrypto2024 · 15,949#2
@Eagles996633 · 2,861#3
@iranairdroper · 18,996#4
@parsv2r1 · 30,816#5
@iran_airdrop_coin · 2,231#6
@cryptomirpto · 1,806#7
@mtpdevelopers · 1,197#8
@Coffe_Web · 2,632#9
@airdropsna · 2,928#10
@DaileCombo · 7,260#11
@ChocolateTargart · 1,332#12
@coiinnews · 1,624#13
@nft_teem · 2,515#14
@biz_bit · 2,787#15
@bt_trade1 · 1,937#16
@Airdrops_0098 · 1,729#17
@crypto_browserr · 12,584#18
@twitter_ekhrajiha · 2,125#19
@MehdiTech_IR · 8,759#20
@iranairdrop888 · 11,350#21
@Dogs_chanls · 562#22
@Airdrops_raygan_moatabar · 1,627#23
@telairdrop20 · 1,644#24
@memefiir · 5,700#25
@airdrop_arzdigital_channel · 2,000#26
@Airdrop_Artificial · 1,843#27
@fxtrad_ir · 647#28
@VPN_V2_NAPS · 2,477#29
@BreakingIranUSA · 2,284#30
@mehrarz_com · 2,003#31
@airderaphmd · 1,469#32
@NordPulse · 4,522#33
@Airdrop_NEWS_Q · 3,159#34
@free_airdropland · 5,554 (as read 29 September 2026)#35
@NetUnblockVPN · 8,310#36
@airdropclubO · 1,664#37
@nilom22m · 30,624#38
@hamsterloppol · 2,605#39
@textcupido · 2,457#40
@SELL_TON_NOT · 835#41
@airdropcrybto2024 · 2,035#42
@kanalkhodrocom · 1,130#43
@LOSTDOGSY · 1,210#44
@GOLDCSALPER20 · 3,852#45
@Diazepamkn · 4,169#46
@Dark_Nero8 · 1,133#47
@faridhossinzadeh_fx · 792#48
@editgandom · 600#49
@Master021solo · 978#50
@akhbar_dogs · 620#51
@nightt_guard · 1,694#52
Read from Telegram’s recommendation API, most recently 29 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@parsv2r1 · 30,816
Telegram ranks this channel #1 of 36 here — alongside 35 others — read 19 September 2026
@iranairdroper · 18,996
Telegram ranks this channel #3 of 56 here — alongside 55 others — read 3 October 2026
@nilom22m · 30,624
Telegram ranks this channel #16 of 50 here — alongside 49 others — read 6 September 2026
@kadbaanooo · 21,265
Telegram ranks this channel #57 of 59 here — alongside 58 others — read 23 September 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 24 October 2026 — this entry's latest reading, not the date you are reading this.
“VINTAGE STATION” (@StationVintage), 19,795 subscribers as measured 24 October 2026. Telegram Register, tgregister.com/channel/StationVintage.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.