Channel
amo.sinas
@amosinas
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,921subscribers
+155 since we began measuring on 20 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001976119172 |
|---|---|
| Type | Channel |
| Username | @amosinas |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 September 2026 |
| Last confirmed live | 6 November 2026 |
| Measurements held | 20 |
| Confirmed unchanged | 1 time, most recently 6 November 2026 |
| On Telegram | t.me/amosinas |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Nov 2026, 07:48 | 2,921 | -6 |
| 3 Nov 2026, 08:29 | 2,927 | -10 |
| 31 Oct 2026, 07:15 | 2,937 | -8 |
| 28 Oct 2026, 01:51 | 2,945 | -11 |
| 21 Oct 2026, 23:27 | 2,956 | -8 |
| 19 Oct 2026, 03:31 | 2,964 | -6 |
| 16 Oct 2026, 08:38 | 2,970 | +4 |
| 13 Oct 2026, 06:37 | 2,966 | -10 |
| 6 Oct 2026, 20:54 | 2,976 | +36 |
| 30 Sept 2026, 02:22 | 2,940 | +122 |
| 16 Sept 2026, 10:37 | 2,818 | +27 |
| 13 Sept 2026, 00:42 | 2,791 | no change |
| 12 Sept 2026, 08:20 | 2,791 | -7 |
| 8 Sept 2026, 09:38 | 2,798 | +26 |
| 3 Sept 2026, 03:08 | 2,772 | -8 |
| 30 Aug 2026, 14:17 | 2,780 | +20 |
| 27 Aug 2026, 21:48 | 2,760 | -2 |
| 24 Aug 2026, 13:05 | 2,762 | -6 |
| 20 Aug 2026, 22:02 | 2,768 | +2 |
| 20 Aug 2026, 02:30 | 2,766 | 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.
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.
@aliahmadiyani_a · 46,753
Telegram ranks this channel #6 of 64 here — alongside 63 others — read 26 August 2026
@dj_myou · 47,192
Telegram ranks this channel #11 of 61 here — alongside 60 others — read 9 September 2026
@hamidreza_babaei_music · 25,988
Telegram ranks this channel #14 of 65 here — alongside 64 others — read 13 September 2026
@Shadmehrsongz · 71,238
Telegram ranks this channel #55 of 83 here — alongside 82 others — read 20 August 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 6 November 2026 — this entry's latest reading, not the date you are reading this.
“amo.sinas” (@amosinas), 2,921 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/amosinas.
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.