Telegram RegisterThe public register of Telegram
Telegram profile photo for ALMIGHTI

Channel

ALMIGHTI

@almightiiiiii

On this record: Topic · Previous handles · Growth · Engagement · Cite this entry

1,563subscribers

No longer on Telegram — last measured 5 October 2026

+78 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001881431666
TypeChannel
Username@almightiiiiii
CreatedBetween 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live5 October 2026
Measurements held16
Confirmed unchanged1 time, most recently 5 October 2026
On Telegramt.me/almightiiiiii

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 34% 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.

Previous handles

@almightiiiiii was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@almightiiiiii
held 27 September 2026 – 27 September 2026

Growth

1,4851,5631,5248 August 2026 — 1,485 subscribers9 August 2026 — 1,489 subscribers12 August 2026 — 1,488 subscribers15 August 2026 — 1,492 subscribers18 August 2026 — 1,493 subscribers21 August 2026 — 1,496 subscribers24 August 2026 — 1,502 subscribers28 August 2026 — 1,505 subscribers31 August 2026 — 1,507 subscribers4 September 2026 — 1,512 subscribers9 September 2026 — 1,523 subscribers13 September 2026 — 1,528 subscribers17 September 2026 — 1,535 subscribers26 September 2026 — 1,551 subscribers27 September 2026 — 1,551 subscribers5 October 2026 — 1,563 subscribers8 August 20265 October 2026
16 measurements spanning 58 days, net +78. 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 1,473–1,575 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Oct 2026, 06:571,563+12
27 Sept 2026, 02:431,551no change
26 Sept 2026, 12:401,551+16
17 Sept 2026, 09:581,535+7
13 Sept 2026, 07:401,528+5
9 Sept 2026, 08:571,523+11
4 Sept 2026, 03:421,512+5
31 Aug 2026, 15:141,507+2
28 Aug 2026, 05:541,505+3
24 Aug 2026, 20:031,502+6
21 Aug 2026, 05:181,496+3
18 Aug 2026, 09:421,493+1
15 Aug 2026, 17:181,492+4
12 Aug 2026, 00:521,488-1
9 Aug 2026, 09:511,489+4
8 Aug 2026, 17:151,485first 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.

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 5 October 2026 — this entry's latest reading, not the date you are reading this.

“ALMIGHTI” (@almightiiiiii), 1,563 subscribers as measured 5 October 2026. Telegram Register, tgregister.com/channel/almightiiiiii.

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.