Channel
1️⃣➖2️⃣➖️3️⃣➖️4️⃣➖️SℹNF.....2026
@BIRINCHI_1
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,959subscribers
+478 since we began measuring on 18 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001395249810 |
|---|---|
| Type | Channel |
| Username | @BIRINCHI_1 |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 21 September 2026 |
| Last confirmed live | 8 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 8 November 2026 |
| On Telegram | t.me/BIRINCHI_1 |
Topic
Local community — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 8 Nov 2026, 01:01 | 1,959 | -16 |
| 4 Nov 2026, 17:36 | 1,975 | -10 |
| 1 Nov 2026, 19:20 | 1,985 | -8 |
| 30 Oct 2026, 01:18 | 1,993 | -10 |
| 26 Oct 2026, 15:38 | 2,003 | -8 |
| 24 Oct 2026, 02:06 | 2,011 | -8 |
| 21 Oct 2026, 08:27 | 2,019 | -1 |
| 18 Oct 2026, 08:39 | 2,020 | -3 |
| 15 Oct 2026, 06:25 | 2,023 | -9 |
| 12 Oct 2026, 13:28 | 2,032 | -16 |
| 5 Oct 2026, 15:37 | 2,048 | +15 |
| 27 Sept 2026, 14:16 | 2,033 | +55 |
| 21 Sept 2026, 02:02 | 1,978 | no change |
| 18 Sept 2026, 08:38 | 1,978 | -5 |
| 13 Sept 2026, 18:57 | 1,983 | +35 |
| 9 Sept 2026, 16:58 | 1,948 | +98 |
| 4 Sept 2026, 18:59 | 1,850 | +108 |
| 1 Sept 2026, 09:46 | 1,742 | +45 |
| 29 Aug 2026, 06:53 | 1,697 | +48 |
| 25 Aug 2026, 21:59 | 1,649 | 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.
@innovatsionmetodika · 26,890
Telegram ranks this channel #16 of 85 here — alongside 84 others — read 19 September 2026
@boshlangich_milliy · 34,530
Telegram ranks this channel #28 of 64 here — alongside 63 others — read 3 September 2026
@ustoz_0307 · 19,324
Telegram ranks this channel #29 of 76 here — alongside 75 others — read 4 October 2026
@birinchisinf · 93,107
Telegram ranks this channel #41 of 76 here — alongside 75 others — read 18 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 8 November 2026 — this entry's latest reading, not the date you are reading this.
“1️⃣➖2️⃣➖️3️⃣➖️4️⃣➖️SℹNF.....2026” (@BIRINCHI_1), 1,959 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/BIRINCHI_1.
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.