Telegram RegisterThe public register of Telegram

Channel

eat.me

@eatdotme

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,497subscribers

-4 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001081559998
TypeChannel
Username@eatdotme
Created9 January 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/eatdotme

Growth

2,4972,5012,4996 August 2026 — 2,501 subscribers6 August 2026 — 2,501 subscribers11 August 2026 — 2,497 subscribers6 August 202611 August 2026
3 measurements spanning 6 days, net -4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 2,496–2,502 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 23:422,497-4
6 Aug 2026, 05:342,501no change
6 Aug 2026, 00:252,501first reading

Engagement

15 posts held, back to 3 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
52.3%
avg views ÷ 2,497 subscribers
Avg views / post
1,310
2 posts measured
Reaction rate
3.44%
reactions ÷ views · ER floor
Posts in window
3
of 15 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held15 (3 June 20264 August 2026)
Views total2,614
Reactions total90
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:26 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
0s
Average length
0s

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.

Reaction mix

536 reactions across 14 posts, in 15 distinct kinds. The most used accounts for 58.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
31158.0%
🔥10920.3%
👍356.53%
😱295.41%
😁142.61%
💯122.24%
🙈81.49%
🎃40.746%
❤‍🔥30.56%
💔30.56%
🤮30.56%
🫡20.373%
10.187%
💩10.187%
🤔10.187%

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 14 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 536reactions 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 4 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.

Recent posts

2 Aug 2026, 04:21 UTC994 views42 reactionsread 7 August 2026
Photo

мегостудни собираются вместе медленно, но верно и в Портленде! с ума можно сойти от того, сколько замечательных и ярких людей я знаю!

27🔥10😁5

22 Jul 2026, 15:48 UTC≈1,620 views48 reactionsread 7 August 2026

https://pdx.eater.com/maps/portland-oregon-best-burgers-restaurants-pdx ну вот и наш меншн в местном Итере, 9 месяцев после открытия.

🔥3612

29 Jun 2026, 22:33 UTC≈2,370 views41 reactionsread 7 August 2026
Photo

так ебут, что даже не уложишь салатик красиво: раздутый рис, арахис, китайская сосиска, мята. Заправочка острая, чтобы слюни текли, но хотелось еще

37🔥4

27 Jun 2026, 19:04 UTC≈2,010 views40 reactionsread 7 August 2026
Photo

в тесноте, да не в обиде

27🔥9👍4

26 Jun 2026, 12:54 UTC≈1,720 views22 reactionsread 7 August 2026
Photo

Испанцы такие, да хули этот ваш американский bbq, хуйнул в коптилку, достал говно и положил на тарелку! Что сами съедите, а что маме дадите?

🙈87😁7

23 Jun 2026, 13:41 UTC≈1,960 views20 reactionsread 7 August 2026
Video

Учитесь, щеглы

7👍5🔥4😁21🤔1

19 Jun 2026, 02:07 UTC≈2,340 views22 reactionsread 7 August 2026
Photo

Так тоже умеем

👍14🎃42❤‍🔥1💩1

16 Jun 2026, 14:04 UTC≈2,200 views70 reactionsread 7 August 2026
Photo

По старой доброй традиции - я не ем на работе. Я знаю, для некоторых ребят стафф мил это перк, но я лично себя никогда не чувствую хорошо после того как ты сел и на нервах затолкал в себя тарелку (разной степени полезности). Моё личное питание в целом очень утилитарное и перформативное. Я ем изо дня одно и то же. На пикче то, на чем я спокойно держусь 10-13 часов: 500г йогурта с грецким орехом, 200г сардин с фасолью

44💯12😱12❤‍🔥2

15 Jun 2026, 22:34 UTC≈1,700 views31 reactionsread 7 August 2026
Photo

Бургеры себя сами летом не продают к сожалению. Точнее продают, но лучше бы еще и готовили себя сами. Это 45 цельсия примерно, но еще наверное поднимется градуса на 3-4 🫠

😱179🔥3🫡2

13 Jun 2026, 12:58 UTC≈1,800 views38 reactionsread 7 August 2026
Photo

ну и игра в кальмара

26👍12

Showing the 12 most recent of 15 posts we hold for @eatdotme. 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.

Citation-graph rank

Citation-graph rank — 831,284 of 1,176,613entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“eat.me” (@eatdotme), 2,497 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/eatdotme.

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.