Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝑺αrα

Channel

𝑺αrα

@axlve

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

12,257subscribers

-344 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001987301685
TypeChannel
Username@axlve
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded20 August 2026
Last confirmed live8 September 2026
Measurements held29
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/axlve

Growth

12,25712,60112,4297 August 2026 — 12,601 subscribers7 August 2026 — 12,600 subscribers8 August 2026 — 12,575 subscribers9 August 2026 — 12,563 subscribers10 August 2026 — 12,560 subscribers11 August 2026 — 12,548 subscribers12 August 2026 — 12,538 subscribers13 August 2026 — 12,534 subscribers14 August 2026 — 12,522 subscribers16 August 2026 — 12,518 subscribers17 August 2026 — 12,515 subscribers18 August 2026 — 12,496 subscribers19 August 2026 — 12,487 subscribers20 August 2026 — 12,486 subscribers20 August 2026 — 12,486 subscribers21 August 2026 — 12,467 subscribers22 August 2026 — 12,458 subscribers24 August 2026 — 12,424 subscribers25 August 2026 — 12,404 subscribers26 August 2026 — 12,391 subscribers27 August 2026 — 12,387 subscribers28 August 2026 — 12,380 subscribers29 August 2026 — 12,367 subscribers31 August 2026 — 12,344 subscribers1 September 2026 — 12,337 subscribers2 September 2026 — 12,326 subscribers3 September 2026 — 12,314 subscribers4 September 2026 — 12,293 subscribers8 September 2026 — 12,257 subscribers7 August 20268 September 2026
29 measurements spanning 32 days, net -344. 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 12,205–12,653 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
8 Sept 2026, 04:1812,257-36
4 Sept 2026, 21:2212,293-21
3 Sept 2026, 08:3612,314-12
2 Sept 2026, 02:5612,326-11
1 Sept 2026, 01:2712,337-7
31 Aug 2026, 02:5312,344-23
29 Aug 2026, 23:2812,367-13
28 Aug 2026, 20:3512,380-7
27 Aug 2026, 19:5812,387-4
26 Aug 2026, 18:1712,391-13
25 Aug 2026, 20:0412,404-20
24 Aug 2026, 18:0412,424-34
22 Aug 2026, 23:4212,458-9
21 Aug 2026, 11:5412,467-19
20 Aug 2026, 18:2512,486no change
20 Aug 2026, 12:1412,486-1
19 Aug 2026, 14:1412,487-9
18 Aug 2026, 16:5512,496-19
17 Aug 2026, 13:2812,515-3
16 Aug 2026, 04:0312,518first reading

Engagement

No public post preview. We read this entry on 20 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under 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.

القرآن الكريم
@The1Holy1Quran1 · 80,518
Telegram ranks this channel #39 of 74 here — alongside 73 others — read 18 August 2026
ثالث عيوني .
@Oh_RR · 38,492
Telegram ranks this channel #44 of 67 here — alongside 66 others — read 31 August 2026
إيلان.
@e0lann · 48,841
Telegram ranks this channel #53 of 82 here — alongside 81 others — read 26 August 2026
عَين
@oeen3 · 68,581
Telegram ranks this channel #54 of 74 here — alongside 73 others — read 20 August 2026
رثاء الحُسين
@alruer · 67,460
Telegram ranks this channel #64 of 78 here — alongside 77 others — read 20 August 2026

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

“𝑺αrα” (@axlve), 12,257 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/axlve.

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.