Telegram RegisterThe public register of Telegram
Telegram profile photo for کانال رسمی کربلایی امیر کرامتی

Channel

کانال رسمی کربلایی امیر کرامتی

@amir_keramati118

On this record: Topic · Growth · Engagement · Citations · Cite this entry

2,176subscribers

-49 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1001065804068
TypeChannel
Username@amir_keramati118
CreatedBetween 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 September 2026
Last confirmed live24 September 2026
Measurements held13
Confirmed unchanged1 time, most recently 24 September 2026
On Telegramt.me/amir_keramati118

Topic

Religion — 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 19 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

2,1762,2252,200.512 August 2026 — 2,225 subscribers16 August 2026 — 2,216 subscribers19 August 2026 — 2,211 subscribers22 August 2026 — 2,210 subscribers25 August 2026 — 2,204 subscribers29 August 2026 — 2,197 subscribers31 August 2026 — 2,192 subscribers3 September 2026 — 2,193 subscribers9 September 2026 — 2,185 subscribers13 September 2026 — 2,182 subscribers16 September 2026 — 2,177 subscribers19 September 2026 — 2,177 subscribers24 September 2026 — 2,176 subscribers12 August 202624 September 2026
13 measurements spanning 44 days, net -49. 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 2,169–2,232 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Sept 2026, 23:572,176-1
19 Sept 2026, 00:532,177no change
16 Sept 2026, 09:382,177-5
13 Sept 2026, 01:362,182-3
9 Sept 2026, 11:372,185-8
3 Sept 2026, 17:162,193+1
31 Aug 2026, 17:042,192-5
29 Aug 2026, 00:262,197-7
25 Aug 2026, 20:542,204-6
22 Aug 2026, 16:162,210-1
19 Aug 2026, 13:342,211-5
16 Aug 2026, 06:082,216-9
12 Aug 2026, 05:312,225first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“کانال رسمی کربلایی امیر کرامتی” (@amir_keramati118), 2,176 subscribers as measured 24 September 2026. Telegram Register, tgregister.com/channel/amir_keramati118.

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.