Channel
@trepetno_agency
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,226subscribers
-1 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002377837846 |
|---|---|
| Type | Channel |
| Username | @trepetno_agency |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/trepetno_agency |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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 |
|---|---|---|
| 16 Sept 2026, 06:40 | 1,226 | +5 |
| 12 Sept 2026, 15:21 | 1,221 | -3 |
| 8 Sept 2026, 23:56 | 1,224 | -3 |
| 3 Sept 2026, 13:37 | 1,227 | +1 |
| 31 Aug 2026, 04:43 | 1,226 | -1 |
| 21 Aug 2026, 21:06 | 1,227 | +1 |
| 18 Aug 2026, 16:25 | 1,226 | -1 |
| 15 Aug 2026, 14:25 | 1,227 | +1 |
| 9 Aug 2026, 03:52 | 1,226 | -1 |
| 8 Aug 2026, 10:19 | 1,227 | first reading |
5 posts held, back to 9 July 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 5 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
18 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 22.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5334871555165931848 | 4 | 22.2% | |
| custom 5348315133514891860 | 4 | 22.2% | |
| custom 5417945658713722241 | 4 | 22.2% | |
| custom 5348360355225552721 | 3 | 16.7% | |
| custom 5345877198408534216 | 2 | 11.1% | |
| custom 5346316333044744120 | 1 | 5.56% |
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 5 of the 5 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 18 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 9 July 2026 to 5 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.
Планы на семейный вечер: собрать всех за одним столом и выбрать, кто сегодня проиграет 😄 Сохраняйте подборку 🎲
custom 53483151335148918603custom 53348715551659318482custom 53458771984085342162
Дайте угадаем, у вас уже был опыт путешествия с няней, после которого вы думали «никогда больше»? Знаем эту боль. В карточках — 5 пунктов, которые важно проверять до поездки. Сохраняйте, чтобы не потерять 👆
custom 54179456587137222412custom 53483603552255527211
🌞 За одной анкетой — большой объём работы, который остаётся за кадром. Подбор начинается задолго до того, как вы знакомитесь с кандидатом. Всё начинается с понимания вашего запроса. Не только обязанностей и графика, но и привычек семьи, ожиданий, темпа жизни и особенностей дома. Именно эти детали помогают найти человека, который действительно вам подойдёт 🫲 Затем — десятки собеседований, проверка рекомендаций, проф…
custom 53348715551659318482custom 53483151335148918601custom 54179456587137222411
Ещё несколько лет назад главным вопросом на собеседовании был: «Сколько лет вы работаете?» 🦋 Сегодня этот вопрос всё чаще уходит на второй план. Потому что опыт сам по себе перестал быть гарантией. Семьи ищут не человека, который просто умеет выполнять свою работу. Они ищут человека, который органично встроится в их образ жизни 🕯️ Мы всё чаще замечаем несколько изменений. ⭐️ Вырос запрос на узкую экспертизу. Есл…
custom 53483603552255527212
Расставание с мамой — стресс для каждого малыша. Даже если няня уже знакомая 🙏 То, как вы скажете «я ухожу», определяет, каким будет день: спокойным или со слезами у двери. В карусели — 5 коротких фраз, которые помогут ребёнку почувствовать себя в безопасности, а вам — уйти без чувства вины. Сохраняйте, чтобы не потерять 🦋
custom 53463163330447441201custom 54179456587137222411
Showing the 5 most recent of 5 posts we hold for @trepetno_agency. 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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Трепетно | Агентство домашнего персонала” (@trepetno_agency), 1,226 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/trepetno_agency.
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.