Channel
@gdecourrier
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
580subscribers
+126 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002771038391 |
|---|---|
| Type | Channel |
| Username | @gdecourrier |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/gdecourrier |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 08:05 | 580 | +96 |
| 23 Aug 2026, 15:25 | 484 | +19 |
| 15 Aug 2026, 02:57 | 465 | +11 |
| 8 Aug 2026, 05:00 | 454 | no change |
| 7 Aug 2026, 17:34 | 454 | first reading |
6 posts held, back to 2 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 6 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
103 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 31.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5215235150941544152 | 32 | 31.1% | |
| custom 5354799404555464150 | 30 | 29.1% | |
| custom 5418102356300546031 | 25 | 24.3% | |
| custom 5217607927099053579 | 16 | 15.5% |
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 6 of the 6 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 103 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 2 August 2026 to 7 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.
знаем, что любители нашего воскресного гадания точно заценят ☀️ нашли это кафе, называется Otsu – не могли вам не показать, а вдруг вы собираетесь в Барселону, девочки 😷
custom 53547994045554641505custom 54181023563005460313custom 52176079270990535792
Краснодар 🍓🫒💁 были буквально 1,5 дня, но какие… #где_путешествие
custom 53547994045554641506custom 52176079270990535794custom 52152351509415441523custom 54181023563005460312
кажется, в интернете наконец-то перестали советовать просыпаться в 5 утра…🧿 собрали 10 привычек, которые считаются здоровыми сейчас, некоторые очень необычные (заодно подтянем английский🧿): 1. low cortisol morning Первые 30–60 минут после пробуждения не берём в руки телефон – проводим утро без новостей, рабочих чатов и скроллинга 2. third place Найти своё уютное третье место помимо дома и работы. Это может быть лю…
custom 53547994045554641508custom 52152351509415441524custom 54181023563005460314custom 52176079270990535792
Любимая вывеска в Женеве и мой пирог с малиной, крыжовником и абрикосами
custom 521523515094154415210custom 53547994045554641506custom 54181023563005460315
девочки, если носите линзы или целыми днями сидите за ноутбуком, сохраняйте 📌 💙 если открыть любую мою сумку, почти всегда найдёте там гилан в мини-капельницах — любимые увлажняющие капли, одна капельница на одно применение, они без консервантов 💙 а дома всегда лежит тауфон — мне они очень быстро помогают от усталости и ощущения песка, моя вечная база знаю о чем говорю, ношу линзы уже почти 20 лет… #где_рекомендац
custom 52152351509415441528custom 54181023563005460316custom 53547994045554641505
по традиции гадаем на грядущую неделю, девочки. выбирай 1 картину и смотри, что там ждёт 🐾🤍
custom 52176079270990535798custom 52152351509415441527custom 54181023563005460315
Showing the 6 most recent of 6 posts we hold for @gdecourrier. 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.
Named by 5 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“где курьер” (@gdecourrier), 580 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/gdecourrier.
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.