Telegram RegisterThe public register of Telegram
Telegram profile photo for Lesia737

Channel

Lesia737

@aviatorLS737

Has discussion group

On this record: Growth · Engagement · Telegram's recommendations · Cite this entry

4,103subscribers

-20 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001743683658
TypeChannel
Username@aviatorLS737
Created11 March 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded4 September 2026
Last confirmed live6 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/aviatorLS737

Growth

4,1034,1234,1136 August 2026 — 4,123 subscribers10 August 2026 — 4,118 subscribers17 August 2026 — 4,121 subscribers20 August 2026 — 4,119 subscribers24 August 2026 — 4,120 subscribers27 August 2026 — 4,121 subscribers30 August 2026 — 4,116 subscribers2 September 2026 — 4,109 subscribers4 September 2026 — 4,109 subscribers6 September 2026 — 4,103 subscribers6 August 20266 September 2026
10 measurements spanning 31 days, net -20. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 4,100–4,126 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Sept 2026, 15:384,103-6
4 Sept 2026, 23:324,109no change
2 Sept 2026, 15:054,109-7
30 Aug 2026, 17:134,116-5
27 Aug 2026, 21:134,121+1
24 Aug 2026, 14:244,120+1
20 Aug 2026, 13:224,119-2
17 Aug 2026, 12:094,121+3
10 Aug 2026, 15:384,118-5
6 Aug 2026, 09:564,123first 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.

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.

Расследования авиакатастроф
@rumayday · 29,845
Telegram ranks this channel #42 of 91 here — alongside 90 others — read 8 September 2026
Smartavia
@Flysmartavia · 43,449
Telegram ranks this channel #43 of 71 here — alongside 70 others — read 28 August 2026
Пристегните ремни | авиация
@premni · 30,606
Telegram ranks this channel #49 of 87 here — alongside 86 others — read 7 September 2026
Авиаторщина
@aviatorshina · 120,788
Telegram ranks this channel #55 of 89 here — alongside 88 others — read 14 August 2026
Шереметьево
@svo_online · 56,992
Telegram ranks this channel #62 of 82 here — alongside 81 others — read 23 August 2026
Авиадиспетчер
@aviadispet4er · 34,415
Telegram ranks this channel #80 of 93 here — alongside 92 others — read 3 September 2026

This channel appears in 6 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“Lesia737” (@aviatorLS737), 4,103 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/aviatorLS737.

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.