PINs Announcement pinned «🎁 Winners list: Tips: PINS token rewards will be sent to the winning address within 24 hours. Each winner will receive 2,000 PINS tokens. EVjqxuifHfVTVtHqr9kW3rMM7YqKyJBsH1dkija5Tnz1eQaLS EWjRqu2CFNboEZKmD3yAAJW98SLy3MwSXWPmWKTTVuGKr7nVW EQuKSnJAGWHRoe3B…»

Channel
PINs Announcement
@pinsnetwork
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
116subscribers
-3 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 | -1001964515465 |
|---|---|
| Type | Channel |
| Username | @pinsnetwork |
| Created | Between 1 April 2023 and 17 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/pinsnetwork |
Topic
Giveaways & airdrops — 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 97% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 12:15 | 116 | -1 |
| 11 Sept 2026, 17:20 | 117 | -1 |
| 14 Aug 2026, 22:16 | 118 | -1 |
| 9 Aug 2026, 04:31 | 119 | no change |
| 7 Aug 2026, 10:28 | 119 | first reading |
Engagement
20 posts held, back to 17 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 14 November 2023. An engagement rate over an empty window would be a number about nothing.
Reaction mix
33 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 11 | 33.3% | |
| 👍 | 10 | 30.3% | |
| 💩 | 8 | 24.2% | |
| 🤡 | 2 | 6.06% | |
| 🥱 | 2 | 6.06% |
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 5 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 33 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 17 October 2023 to 14 November 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.
Recent posts
🎁 Winners list: Tips: PINS token rewards will be sent to the winning address within 24 hours. Each winner will receive 2,000 PINS tokens. EVjqxuifHfVTVtHqr9kW3rMM7YqKyJBsH1dkija5Tnz1eQaLS EWjRqu2CFNboEZKmD3yAAJW98SLy3MwSXWPmWKTTVuGKr7nVW EQuKSnJAGWHRoe3Bd1G1GehnD3RsxkwcMMD1w3D5hzEoJrHo8 EctysLVxFQUZCXB1GKj4wAxvs2Ss73uwHLDFiwZuf3xhmaghS EV9cgkjKuuFjUQQdYzVtk3c8wiong2dp4owcZ3eGJAPWK45ve EGZcyZSgJX5iFexUMHkPHpaXgw16pZg…
🔥11💩5👍3🤡2🥱2
PINs Announcement pinned a photo
🔥NOKI Feeding Competition Total Rewards: 60,000 PINS tokens 🌐Competition Rules: You need to feed NOKI as much as possible. The top 30 users with the most 'friendship' gained by NOKI during the competition period, will each receive 2,000 PINS tokens. 🕰Competition start and end time: November 7th, 14:00 PM UTC - November 13th, 14:00 PM UTC 💥Competition results will be announced on telegram: https://t.me/pins_network…
👍3
PINs Announcement pinned a photo
👍Someone just bought a NOKI with 5,001 friendship points for a hefty 0.02ETH! 🔥There are 93 NOKI owners on opensea now. https://opensea.io/collection/pinsnetworknoki/activity
PINs Announcement pinned «Winners list: https://pins.network/4Z9eJjXRoXs https://pins.network/4Z8vVDHbGWC https://pins.network/4Z8QT7KtqRw https://pins.network/4ZbhEsj2fQy https://pins.network/4XeecVUgRt7 Please contact @Eric_PINs and claim your reward!»
Winners list: https://pins.network/4Z9eJjXRoXs https://pins.network/4Z8vVDHbGWC https://pins.network/4Z8QT7KtqRw https://pins.network/4ZbhEsj2fQy https://pins.network/4XeecVUgRt7 Please contact @Eric_PINs and claim your reward!
PINs Announcement pinned a photo
🔥Joke Creation Contest 🎁Rewards: 10,000 PINS tokens 🌐Rules: 1⃣ Open the PINs App, tap the "+" icon on the top right, and create a Verse. 2⃣ Then, craft a joke within the Verse. 3⃣ DM @Eric_PINs on Telegram and send him the link of your Verse. 🕰Deadline: October 26th, 14:00 PM UTC. 🎉The PINs team will randomly select 10 high-quality jokes. Each winner will receive 1,000 PINS tokens. Tips: 🔷The more captivating th…
👍1
👍5001 Friendship Points https://opensea.io/assets/ethereum/0xc47e7dd324281895f87f1e19c1fbd36ef528cd75/403/
PINs Announcement pinned «👍Fantastic story from the Verse. 🔥As long as you have NOKI, you can create Verse and then create stories in Verse. #NOKI #Verse 🎁Creating stories in Verse is also one of the main ways to PINs tokens from the PINs network in the future! https://pins.networ…»
Showing the 12 most recent of 20 posts we hold for @pinsnetwork. 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
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“PINs Announcement” (@pinsnetwork), 116 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/pinsnetwork.
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.