Channel
@nosikthepitbull
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
545subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001764553860 |
|---|---|
| Type | Channel |
| Username | @nosikthepitbull |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 12 September 2026 |
| On Telegram | t.me/nosikthepitbull |
Personal blog — 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 91% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 01:37 | 545 | +1 |
| 27 Aug 2026, 07:09 | 544 | +1 |
| 21 Aug 2026, 03:36 | 543 | +2 |
| 14 Aug 2026, 06:54 | 541 | -4 |
| 6 Aug 2026, 21:31 | 545 | no change |
| 6 Aug 2026, 21:19 | 545 | first reading |
9 posts held, back to 3 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
364 reactions across 9 posts, in 5 distinct kinds. The most used accounts for 28.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5253802350941858699 | 103 | 28.3% | |
| custom 5219949238326145603 | 91 | 25.0% | |
| custom 5233353367400504577 | 89 | 24.5% | |
| custom 5420573392719862417 | 65 | 17.9% | |
| custom 5235728802142759605 | 16 | 4.40% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 9 of the 9 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 364 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 3 August 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
поставила будильник сегодня на 6:00, в итоге вышли в 6:50 — считаю, успех ахахах успели вполне комфортно по лесу часик пошататься. попозже поехала на командную съемку cheers 📷 Москва пздц нагрелась, невозможно на улице находиться…. все, кто любят/ждут жару, — рада за вас, но не от всего сердца ахах из последних сил иду домой к кондейчику…
custom 521994923832614560320custom 54205733927198624175
пополняем водный баланс после усердной работы носом 💧
custom 525380235094185869926custom 54205733927198624176custom 52199492383261456035custom 52333533674005045772custom 52357288021427596051
групповой поиск корминок! 🐽
custom 525380235094185869930custom 52333533674005045773
🌟🌟🌟
custom 525380235094185869922custom 52333533674005045779custom 54205733927198624177
доброе подружковое! ☀️ встретили у пруда наших знакомых девчонок — Лорка (стаффбуль) вообще одна из первых подружек Носа за все ее 6+ лет дома 🤤 периодически встречаемся в мещере, наблюдаем, как девки меняются (:
custom 521994923832614560329custom 542057339271986241717custom 52333533674005045772custom 52538023509418586991
какой классный фотоотчет с пушистой вечеринки Лавки получился! 💙 🤩 на нас: футболки simple dog 🤩 на ребятах: амуниция шарик дог
custom 542057339271986241725custom 52333533674005045773custom 52538023509418586992custom 52357288021427596051
ДЕНЬ РАЗОРЕНИЯ 🤑
custom 523335336740050457733custom 52538023509418586993custom 54205733927198624172custom 52199492383261456031
заснула с самым красивым видом……….. 😚
custom 521994923832614560336custom 525380235094185869915custom 523572880214275960513custom 54205733927198624171
с первым днем отпуска меня! 🤗 только на основной работе ахаха планов особо нет, буду много гулять, встречаться с подругами — только на середину августа кое-что наметили, пока оставлю в секрете 🤭
custom 523335336740050457737custom 52538023509418586994custom 54205733927198624172custom 52357288021427596051
Showing the 9 most recent of 9 posts we hold for @nosikthepitbull. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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.
Names
Channels on the register whose handles appear in this channel's 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.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“ушки gang” (@nosikthepitbull), 545 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/nosikthepitbull.
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.