Channel
๐๐ผ๐ฝ๐๐๐๐๐ผ๐๐๐
@tabrik_loyihaa
On this record: Topic ยท Growth ยท Engagement ยท Citations ยท Cite this entry
4,897subscribers
+978 since we began measuring on 6 August 2026
Risers and fallers across the register ยท movement among entries of 3,162โ10,000.
Register entry
| Telegram ID | -1002215182758 |
|---|---|
| Type | Channel |
| Username | @tabrik_loyihaa |
| Created | Between 1 June 2024 and 30 September 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/tabrik_loyihaa |
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 13 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 22:21 | 4,897 | -28 |
| 12 Sept 2026, 08:37 | 4,925 | +582 |
| 8 Sept 2026, 14:38 | 4,343 | -142 |
| 3 Sept 2026, 19:05 | 4,485 | no change |
| 3 Sept 2026, 13:40 | 4,485 | +355 |
| 31 Aug 2026, 02:47 | 4,130 | +188 |
| 27 Aug 2026, 17:38 | 3,942 | -83 |
| 25 Aug 2026, 02:53 | 4,025 | -195 |
| 22 Aug 2026, 03:19 | 4,220 | -178 |
| 18 Aug 2026, 20:16 | 4,398 | -125 |
| 16 Aug 2026, 03:07 | 4,523 | +235 |
| 12 Aug 2026, 21:54 | 4,288 | +178 |
| 9 Aug 2026, 21:52 | 4,110 | +276 |
| 6 Aug 2026, 21:40 | 3,834 | -85 |
| 6 Aug 2026, 02:48 | 3,919 | 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
@engyangi_fasonlar ยท 75,22643 posts๐ฅ๐ฅ๐๐ขโ๐ญ๐๐๐๐๐ ๐ฆ๐๐๐ฌ๐๐ข๐๐๐ฅ๐๐ฅ๐ฅ
@chiroylirasmlar_olamii ยท 14,28917 posts๐ฅ๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐ฅ
@tikuvchilik_olamida ยท 26,34815 postsะจะธัะธะฝ ัะธะปะฐะบะปะฐั
@dunyo_tilaklari ยท 1721 post๐ฅ๐๐๐ฆ๐ข๐ก๐ฅ
@engyangifasonlarr ยท 5,8711 post
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.
Mentions
Named by 120 registered channels โ 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@engyangi_fasonlar ยท 75,22699 posts๐ฅ๐๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐๐ฅ
@tikuvchilik_olamida ยท 26,34848 posts๐ฅ๐ฅ๐๐ขโ๐ญ๐๐๐๐๐ ๐ฆ๐๐๐ฌ๐๐ข๐๐๐ฅ๐๐ฅ๐ฅ
@chiroylirasmlar_olamii ยท 14,28947 postsะจะธัะธะฝ ัะธะปะฐะบะปะฐั
@dunyo_tilaklari ยท 1729 posts๐น๐๐โ๐๐๐๐ ๐๐๐ ๐๐๐๐๐น
@Qosimova_Nodi ยท 35,6139 postsโค๏ธSAIDORAโค๏ธ HIKOYALARI๐
@Saidora_hikoyalari ยท 32,4108 postsะะะะะะ.
@AZIZIM_2024 ยท 66,4387 postsBaxtli Oilam๐บ
@BaxtliOilam_uz ยท 74,3267 postsโป๏ธ ะะตัะตั ะพะดะฝะธะบ โป๏ธ
@Hayitova_charos ยท 667 posts๐๐๐๐๐๐๐๐ ๐๐๐๐๐๐๐
@saylanma_asarlar ยท 45,6677 posts๐๊ฏญ๐๐๊ฏญ๐๐๊ฏญ๐๊ฏญ๐๊ฏญ ๐๊ฏญ๐๊ฏญ๐๊ฏญ๐๊ฏญ๐๊ฏญ๐๊ฏญ
@Atirgul_kanali ยท 44,0796 posts๐๐๐๐๐๐ สแดsสษชสแดsษช ๐ฆข
@Nasema_hoshiyasi ยท 57,7126 postsะจะะะะะะะ_ะธะถะพะดะธ
@shaydoyim_ijodi ยท 44,4676 posts๐ฌ๐ข๐ฃ๐๐ค ๐๐๐๐ง๐๐ฅ
@YOPIQ_DAFTAR ยท 47,7486 posts๐ฅ๐๐๐ฆ๐ข๐ก๐ฅ
@engyangifasonlarr ยท 5,8715 postsFasonlar olami โค๐
@Fasonlar_modalar_olami1 ยท 37,1205 posts๐๐๐๐๐ ๐๐๐๐๐๐๐๐
@Hayot_shahrida ยท 43,3775 postsโ๐ธโะะฃะ ะะ ะะจะฅะะะะ๐ธโ
@nurlioshxona ยท 44,7365 postsาะาะะฃะก. ะะฐัััะฝะฐ ะะฑะดัะปะปะฐะตะฒะฐ ะธะถะพะดะธ.
@Qaqnus_1991_M_A ยท 80,2135 postsRETRO HIKOYALAR
@retrohikooyalar ยท 60,1925 postsSalatlar Retseptlari
@SALATLAR_RETSEPTI_AYOLLAR_KANALI ยท 35,4575 postsGOLD VIDEO
@Tezkor_xabarlar_foydali_videolar ยท 27,2815 postsTikuvchilar-Fasonlar
@tikuvchilar_andozalar ยท 18,8235 postsUMR HIKOYALARI
@Umr_hikoyalari ยท 26,3465 posts
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.
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 15 September 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐ผ๐ฝ๐๐๐๐๐ผ๐๐๐โ (@tabrik_loyihaa), 4,897 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/tabrik_loyihaa.
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.