Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 65% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
5 measurements spanning 38 days, net -3. 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 130–133 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
14 Sept 2026, 09:56
130
-1
29 Aug 2026, 13:54
131
-1
23 Aug 2026, 09:58
132
-1
9 Aug 2026, 00:16
133
no change
6 Aug 2026, 23:48
133
first reading
Engagement
20 posts held, back to 13 October 2023 — 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 20 posts for this entry, the most recent from 17 October 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Video runtime
16s
Average length
16s
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
242 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 32.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
79
32.6%
🔥
73
30.2%
👍
37
15.3%
💩
17
7.02%
🥰
16
6.61%
👏
8
3.31%
❤🔥
5
2.07%
👎
3
1.24%
🤡
2
0.826%
😭
1
0.413%
🤪
1
0.413%
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 19 of the 20 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 242 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 13 October 2023 to 17 October 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Share.friend bot is working well 🐰
The bot has been shared many potential projects such as $Wapple and $Kek, as well as the project from OP, which is still sideways with a 1M cap.
Join us, and let's print 🤑
Share.friend Station: Telegram | X | Website
🐰 After launching for 8 hours, Share.friend has reached:
- $546.13K 24H Volume
- 2x ATH from listing price
- 296 Holders
- $61K Mcap
- Many Callers posted about us
- Listing on CMC and CGK soon
Next, we will release some new features and close the Private group for Holders only
Share.friend Station: Telegram | X | Website
🐰 Share.friend is now launched 🥳🔥
👉 Official CA: 0x242914f264d44E4C5eAd31092EC133dCB6C4d73F
👉 Chart: https://www.dextools.io/app/ether/pair-explorer/0x648b0f1381cdd33b9d6051729a3b0d4a7420cd08
If you missed the Fair Launch, this is your chance now to own Keys, unlock all the Rooms on friend.tech 👍
Share.friend Station: Telegram | X | Website
Only 1 hour left until Share.friend launch 🐇
Get ready for takeoff and always beware of scammers and fake contracts 😍
Share.friend Official CA: 0x242914f264d44E4C5eAd31092EC133dCB6C4d73F
Share.friend Station: Telegram | X | Website
🐰 Real-Time Wallet Monitoring for Chosen Traders
With this powerful tool, you can closely track the wallets of your selected traders in real-time. By monitoring their wallet activities as they happen, you'll receive valuable insights that can inform your own trading decisions and investment strategies.
Don't forget that Share.friend will launch at 1AM UTC Oct 17 - only 9 hours left. After launch, many interesting a…
🐰 Launch Announcement 🐇
This may be the information that you are waiting for 🤑🤑
The launch time is 1 AM UTC Oct 17. In this time, we will focus on Marketing and will continuously update about the privilege for Holders, and all other features that we are developing in Share.friend ecosystem.
Share.friend Official CA: 0x242914f264d44E4C5eAd31092EC133dCB6C4d73F
Share.friend Station: Telegram | X | Website
🐰 Time up!! The Fair Launch is ended with 44 ETH raised!
Congrats to Share.friend and all holders!! We will mute the chat until launch to avoid scammers or fake bot that may harm users.
Launch time will be announced in a few minutes
Share.friend Station: Telegram | X | Website
🐰 Private group and 60% profit exclusively for Holders
Holders will be added to our Private group, which is still public now for everyone to experience. In this group, our TG Bot will send the information of Influencer’s Rooms.
👉 Group link: https://t.me/+HQHhEwIx37szM2Q1
Also, Holders will received 60% of our profit. The other 40% is used for Marketing campaign. This will be a special privilege for Holders only.
…
🐰 26 ETH raised in the last 30 minutes and Share.friend is now on Top 1 Pinksale Trending 🔥🔥
https://www.pinksale.finance/launchpad/0x9c762982cfaC070438152fED393f60f562a32ef9?chain=ETH
The Fair Launch is coming to an end now. Owning a Ticket to open all the Rooms on friend.tech will help you earn more in this bullish market. Tickets for Keys to join Private Rooms are limited, are you having it now??
Share.friend S…
❤2👍1🔥1
Showing the 12 most recent of 20 posts we hold for @ShareFriendERC. 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 1 registered channel — 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.
Handles this channel named that no longer answer
Dead references
5
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
5
vacant every time we have ever looked
@ShareFriendERC named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@duckscallseth named in 1 post, 9 August 2026 – 9 August 2026
@insiderasadev named in 1 post, 9 August 2026 – 9 August 2026
@owacryptocomm named in 1 post, 9 August 2026 – 9 August 2026
@richgirleth named in 1 post, 9 August 2026 – 9 August 2026
@tideneth named in 1 post, 9 August 2026 – 9 August 2026
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 14 September 2026 — this
entry's latest reading, not the date you are reading this.
“Share.Friend” (@ShareFriendERC), 130 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/ShareFriendERC.
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.