Telegram RegisterThe public register of Telegram
Telegram profile photo for Bellingham Family

Channel

Bellingham Family

@bellinghamfm

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

174subscribers

-24 since we began measuring on 13 August 2026

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

Register entry

Telegram ID-1004348174556
TypeChannel
Username@bellinghamfm
Created6 July 2026measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live11 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/bellinghamfm

Growth

17419818613 August 2026 — 198 subscribers14 August 2026 — 195 subscribers21 August 2026 — 192 subscribers27 August 2026 — 187 subscribers3 September 2026 — 182 subscribers11 September 2026 — 174 subscribers13 August 202611 September 2026
6 measurements spanning 29 days, net -24. 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 170–202 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 20:36174-8
3 Sept 2026, 12:59182-5
27 Aug 2026, 15:18187-5
21 Aug 2026, 14:35192-3
14 Aug 2026, 19:38195-3
13 Aug 2026, 14:49198first reading

Engagement

11 posts held, back to 6 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 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 11 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

29 reactions across 3 posts, in 9 distinct kinds. The most used accounts for 13.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5307840499883737936413.8%
custom 5309788091458812770413.8%
custom 5310196057517359903413.8%
custom 5307683046382663358310.3%
custom 5307831875589405905310.3%
custom 5307887903437782203310.3%
custom 5307958594304506604310.3%
custom 5310080175004746212310.3%
custom 531001415706243831426.90%

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 3 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 29 reactions 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 6 July 2026 to 20 July 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

20 Jul 2026, 15:34 UTC236 views1 reactionsread 13 August 2026
File

cr: Alinur id: Not our

custom 53076830463826633581

Signed aassex

13 Jul 2026, 18:26 UTC613 viewsread 13 August 2026
Sticker

Sticker, posted without a caption

Signed beks bellingham

12 Jul 2026, 09:49 UTC665 viewsread 13 August 2026

На рп 1. Набор в чат 2. Набор на союзы

Signed

12 Jul 2026, 09:46 UTC923 viewsread 13 August 2026

🤩Bellingham в поисках союзов🤩 ✍️канал ✍️правила ✍️следящий

Signed beks bellingham

6 Jul 2026, 12:08 UTC≈1,190 views16 reactionsread 13 August 2026
Photo

🎤Bellingham family opens the recruitment in the chat. What do you need to do to join the family?🤩 ⌨️ Subscribe to channel 🤩 ⌨️ Read the rules 🤩 ⌨️ Put the last name 🤩 ⌨️ Apply to chat 🤩

custom 53078404998837379363custom 53078879034377822032custom 53079585943045066042custom 53097880914588127702custom 53100801750047462122custom 53101960575173599032custom 53076830463826633581custom 53078318755894059051

Signed DinS

6 Jul 2026, 12:04 UTC633 views12 reactionsread 13 August 2026
Photo

Patent 🤩 Rules 🤩 union 🤩🤩🤩🤩 boost 🤩 Admins Archive 🤩

custom 53078318755894059052custom 53097880914588127702custom 53101960575173599032custom 53076830463826633581custom 53078404998837379361custom 53078879034377822031custom 53079585943045066041custom 53100141570624383141

Signed DinS

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

Mentions

Named by 2 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.

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.

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

“Bellingham Family” (@bellinghamfm), 174 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/bellinghamfm.

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.