Channel
@pitomnikbusji
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
47subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002218637587 |
|---|---|
| Type | Channel |
| Username | @pitomnikbusji |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/pitomnikbusji |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 23:37 | 47 | +1 |
| 3 Sept 2026, 20:02 | 46 | +1 |
| 10 Aug 2026, 15:01 | 45 | no change |
| 6 Aug 2026, 20:18 | 45 | first reading |
15 posts held, back to 3 June 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 15 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
237 reactions across 15 posts, in 14 distinct kinds. The most used accounts for 21.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5816619869046577656 | 51 | 21.5% | |
| custom 5816705132737338493 | 38 | 16.0% | |
| 🙏 | 32 | 13.5% | |
| ❤🔥 | 19 | 8.02% | |
| custom 5816465138554772299 | 18 | 7.59% | |
| custom 5816401714772718786 | 17 | 7.17% | |
| ❤ | 16 | 6.75% | |
| 💋 | 15 | 6.33% | |
| custom 5816895322479139906 | 9 | 3.80% | |
| 🍓 | 9 | 3.80% | |
| custom 5816487962010983512 | 7 | 2.95% | |
| custom 5913385512290228893 | 4 | 1.69% | |
| custom 5818785301362908629 | 1 | 0.422% | |
| 💘 | 1 | 0.422% |
Custom emoji. 8 of the rows above are 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 15 of the 15 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 237 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 3 June 2026 to 1 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.
Опа референс для моей ос🎈 Очень буду рада активу!! Потому-что я потратила на нее очень много времени🎈 (Скину файлом в комментарии для хорошего качества)🌟
❤🔥5💋4🙏2custom 58166198690465776562🍓1custom 58164017147727187861custom 58164651385547722991custom 58167051327373384931
Быстрый чиби арт честь др @jajafree 🎈
❤6custom 58167051327373384935🙏3❤🔥1💋1custom 58164017147727187861custom 58164651385547722991custom 58166198690465776561
Десятый реквест для @treueundhoffnung 🎈
custom 58167051327373384935🍓4💋2🙏2💘1custom 58164017147727187861custom 58164651385547722991custom 58166198690465776561
Артик в честь днюшки красоточки 🎈 (Про реквесты я не забыла, они будут следующими)🎈
custom 58166198690465776567🙏5custom 58164017147727187864custom 58167051327373384932
Гифт для @M4D_DOG в честь ее др🎈
custom 58166198690465776568custom 58167051327373384937💋3❤2custom 58164651385547722991custom 58164879620109835121
И еще одна дополнительная плюшка. Наши сладкие наркоманчики с @jenwoas 😶
custom 58166198690465776565custom 58168953224791399065🙏1
Трейд с @jenwoas 😜 Ребята не колимся если что🎈
custom 58164651385547722996custom 58164879620109835124custom 58168953224791399064🙏1
Девятый реквест для @Shang_Art 🎈
custom 58167051327373384935🙏4custom 58164017147727187864custom 58166198690465776563❤1
Вот они, слева направо 🌟 Цветные скетчи для @socacoca, все персонажи принадлежат ей😜
❤3custom 58167051327373384933🙏2custom 59133855122902288932custom 58164879620109835121
трейд!! не употребляйте кстати
💋5
Ммм рыбка🌟 Восьмой реквест для @KNlFEPLAY 😜
custom 58167051327373384936🙏5custom 58164017147727187864custom 58166198690465776563custom 58164651385547722992custom 59133855122902288931
Балуюсь со стилем и рендером🌟 Вроде как, вышло очень даже миленько. Так что лицезрейте цветной скетч фембойчика..😶
custom 58166198690465776568❤🔥5🍓4🙏2custom 58164017147727187861
Showing the 12 most recent of 15 posts we hold for @pitomnikbusji. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“Питомник” (@pitomnikbusji), 47 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/pitomnikbusji.
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.