Telegram RegisterThe public register of Telegram

Channel

COAST FESS

@CoastFess

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

2,447subscribers

+61 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-1001878404790
TypeChannel
Username@CoastFess
CreatedBetween 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/CoastFess

Growth

2,3862,4472,416.56 August 2026 — 2,386 subscribers7 August 2026 — 2,386 subscribers10 August 2026 — 2,447 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net +61. 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,377–2,456 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 16:512,447+61
7 Aug 2026, 08:582,386no change
6 Aug 2026, 17:482,386first reading

Engagement

28 posts held, back to 6 August 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
3.13%
avg views ÷ 2,447 subscribers
Avg views / post
76.7
28 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
28
of 28 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 7 August 2026
Posts held28 (6 August 20267 August 2026)
Views total2,147
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:36 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
34s
Average length
34s

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.

Recent posts

7 Aug 2026, 16:00 UTC27 viewsread 7 August 2026

Following our weekly evaluations of the Persona Project, we have decided to revise its schedule due to participation levels not meeting the engagement we had anticipated. After reviewing the number of submissions received across each weekly session, we believe that a less frequent schedule will allow the event to remain meaningful while encouraging stronger participation. Effective immediately, the Persona Project w

7 Aug 2026, 15:13 UTC40 viewsread 7 August 2026

The gates for today’s Persona Project are officially closed. Thank you so much to everyone who participated! We wish you nothing but the best as you build beautiful memories with your new friends and family. Before we part ways for now, please remember to keep speaking up against the genocide in Palestine. Let’s stay informed and keep sharing updates regarding the ongoing crises in Indonesia, Iran, Lebanon, Sudan, an

7 Aug 2026, 13:31 UTC66 viewsread 7 August 2026
Photo

Currently waiting for my new pals to pick up the phone 😁... Jakarta feels emptier without a friend, so, perhaps a company would help? I can fish, cook, and work from 9 - 8. I am still very young and you can trust me... So before this call turns into a voice message, call me at @Menjaala.

7 Aug 2026, 13:15 UTC69 viewsread 7 August 2026

⏰ It’s 20.15 WIB! The wait is over. You may now send your self-promotion content to our bot right here: @ Lost at the sea. Note: Once the bot link is removed from this post, please do not send any more submissions. Enjoy making new connections, dearest Tides! 💙

7 Aug 2026, 10:15 UTC85 viewsread 7 August 2026

Friday is here, and so is the Persona Project! Whether you are searching for your next best friend, looking to find your family, or wanting to build a brand-new circle, this is your day to shine! 💡 HOW TO JOIN? Just draft your self-promotion message and submit it to our bot once it goes live. 🔗 Click here to read the full explanation. 🔗 Click here to check out some examples for inspiration. ⚠️ IMPORTANT GUIDELINES

6 Aug 2026, 15:43 UTC122 viewsread 7 August 2026

Looks like it’s about time for me to call it a night. It’s already past midnight here, so I think I’ll browse my Kindle and read a chapter or two before I finally get some sleep. That means I’ll be ending today’s shift here. Thank you so much for bringing such incredible energy to my shift, dearest Tides. 💙 Sharing this time with you all has been an absolute blast, and I’m already looking forward to swimming back to

6 Aug 2026, 15:34 UTC104 viewsread 7 August 2026
Photo

#Undertow. Was literally just adjusting my camera shutter speed and testing the lighting on the water, thinking nothing was going to happen. Then boom, an actual orca glides right past the boat. Best accidental photobomb in history 😳🫨.

Showing the 12 most recent of 28 posts we hold for @CoastFess. 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 — 81,960 of 1,160,990entries 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

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.

Mentions

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

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

“COAST FESS” (@CoastFess), 2,447 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/CoastFess.

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.