Channel
@Sunshinmates
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
31subscribers
-2 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002107279293 |
|---|---|
| Type | Channel |
| Username | @Sunshinmates |
| Created | Between 1 November 2023 and 15 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 4 times, most recently 14 September 2026 |
| On Telegram | t.me/Sunshinmates |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 15:16 | 31 | -2 |
| 15 Aug 2026, 07:15 | 33 | no change |
| 15 Aug 2026, 07:01 | 33 | first reading |
16 posts held, back to 15 January 2024 — 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 16 posts for this entry, the most recent from 3 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.
129 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 22.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5274017417679349304 | 29 | 22.5% | |
| custom 5274113719436061148 | 24 | 18.6% | |
| custom 5271692865414636615 | 23 | 17.8% | |
| custom 5274273058427775436 | 15 | 11.6% | |
| custom 5274088400603852299 | 12 | 9.30% | |
| custom 5271789996100038035 | 11 | 8.53% | |
| custom 5274017512168630613 | 9 | 6.98% | |
| custom 5271892233501550327 | 6 | 4.65% |
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 7 of the 16 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 129 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 15 January 2024 to 3 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.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 19 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
Always, SunShin🤜🏻🤛🏻
Photo, posted without a caption
SunShin🙂🙂
Photo, posted without a caption
custom 52740174176793493045custom 52740175121686306133custom 52742730584277754363custom 52718922335015503272custom 52741137194360611481
Happy mensive, my lovely sunshin
Gak kembaran meriang
custom 52742730584277754368custom 52740174176793493045custom 52717899961000380353custom 52740175121686306131
Bang
custom 52741137194360611486custom 52740175121686306135custom 52717899961000380354custom 52718922335015503274custom 52716928654146366151
Two chopper, two hundred shots🪩
🔠🔠🔠 🔠🔠🔠🔠 🔠☀️
Kindest regards. ☀️ Greetings to all @Sunshinmates enthusiasts and others. ✨ Firstly, I apologize for the delayed response to the subs-for-subs invitation earlier today. Because we receive lots of invitations, Thanks a lot for the enthusiasm! 🌟 Additionally, I apologize for not communicating earlier that we are currently not participating in subs-for-subs since this afternoon, due to overwhelming circumstances and d…
custom 52716928654146366159custom 52740174176793493048custom 52742730584277754364custom 52741137194360611482
Showing the 12 most recent of 16 posts we hold for @Sunshinmates. 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 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Sunshin Housemates” (@Sunshinmates), 31 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/Sunshinmates.
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.