Telegram RegisterThe public register of Telegram
Telegram profile photo for Gamarjoba Tomi

Channel

Gamarjoba Tomi

@GamarjobaTomi

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

460subscribers

-1 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001625652090
TypeChannel
Username@GamarjobaTomi
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/GamarjobaTomi

Growth

460461460.57 August 2026 — 461 subscribers8 August 2026 — 461 subscribers16 August 2026 — 460 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net -1. 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 460–461 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 07:23460-1
8 Aug 2026, 04:49461no change
7 Aug 2026, 18:29461first reading

Engagement

11 posts held, back to 30 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
31.1%
avg views ÷ 460 subscribers
Avg views / post
143
11 posts measured
Reaction rate
12.8%
reactions ÷ views · ER floor
Posts in window
11
of 11 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 6 August 2026
Posts held11 (30 July 20266 August 2026)
Views total1,576
Reactions total202
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 04:49 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.

Reaction mix

202 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 17.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53233367247078304783617.8%
custom 53438343788185707303115.3%
💘2914.4%
custom 53235103788255436952210.9%
custom 5283108072443636277178.42%
custom 5386742154372607013178.42%
🤣157.43%
custom 5323654251640025781115.45%
94.46%
custom 540438009899861150462.97%
custom 534596843210385858741.98%
💯31.49%
😍20.99%

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 areTelegram’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 11 of the 11 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 202reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 30 July 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.

Recent posts

6 Aug 2026, 06:50 UTC79 views11 reactionsread 8 August 2026
Photo

Как красиво господи боже мой…💔

custom 53438343788185707305custom 53235103788255436953custom 53236542516400257813

4 Aug 2026, 17:45 UTC125 views12 reactionsread 8 August 2026
Photo

Муки выбора…

🤣8custom 52831080724436362772custom 53235103788255436952

3 Aug 2026, 20:17 UTC145 views22 reactionsread 8 August 2026
Photo

Welcome home my new one 💔👜

💘8custom 52831080724436362776custom 53233367247078304786😍2

3 Aug 2026, 18:26 UTC143 views31 reactionsread 8 August 2026
Photo

Mommy 💛🍋

💘11custom 534383437881857073010custom 53233367247078304786custom 53235103788255436954

2 Aug 2026, 14:07 UTC148 views17 reactionsread 8 August 2026
Photo

Ходили на обед в «Горыныч», мне тут оооочень вкусно 💛 Так вкусно, что еду не успели сфоткать 😂, особенно суши из мраморной говядины полюбились 😍 Такими темпами у меня будет фуд блог скоро 😂

🤣75custom 53867421543726070134custom 53233367247078304781

1 Aug 2026, 18:06 UTC157 views14 reactionsread 8 August 2026
Photo

В «Фамилии» всегда можно найти красивую посуду, без этих креманок не смогли уйти 🤩🤩

custom 53235103788255436958custom 53233367247078304783custom 53438343788185707303

1 Aug 2026, 10:07 UTC153 views20 reactionsread 8 August 2026
Photo

Все подружки знают, что я люблю чашечки ☕️🏺 Эту подружка привезла из Питера 🩷

custom 53233367247078304787custom 532351037882554369554custom 53438343788185707304

31 Jul 2026, 20:30 UTC150 views21 reactionsread 8 August 2026
Photo

me, myself and I 💚🪸🤩

custom 53867421543726070138custom 52831080724436362775custom 53233367247078304785custom 53438343788185707303

31 Jul 2026, 05:34 UTC160 views19 reactionsread 8 August 2026
Photo

Наведались в «Амуру», меня подкупила розовая матча, за ней еще точно вернусь, но в целом всё вкусно было 🫧💚

custom 53236542516400257818custom 53867421543726070135💘3custom 53438343788185707303

30 Jul 2026, 18:44 UTC155 views19 reactionsread 8 August 2026
Forwarded from @omsroses

если это не произойдёт так, как вы хотели, это произойдёт лучше, чем предполагалось. в этом и есть красота Божьего плана. 🌸

custom 53233367247078304788💘4custom 52831080724436362774💯3

30 Jul 2026, 06:43 UTC161 views16 reactionsread 8 August 2026
Photo

А если еще все это есть из красивой посуды, то вкус увеличивается х100 🤣 или ,как говорится, «не тех тарелочниц боитесь» 🤣🤣🤣

custom 54043800989986115046custom 53459684321038585874💘3custom 53438343788185707303

Showing the 11 most recent of 11 posts we hold for @GamarjobaTomi. 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.

Forward network

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.

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

“Gamarjoba Tomi” (@GamarjobaTomi), 460 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/GamarjobaTomi.

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.