Channel
@WAGMIVillage
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
360subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001739898992 |
|---|---|
| Type | Channel |
| Username | @WAGMIVillage |
| Created | Between 1 December 2021 and 15 August 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 3 times, most recently 13 September 2026 |
| On Telegram | t.me/WAGMIVillage |
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 22 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 29 Aug 2026, 13:55 | 360 | -1 |
| 23 Aug 2026, 02:15 | 361 | -1 |
| 7 Aug 2026, 23:14 | 362 | no change |
| 7 Aug 2026, 04:17 | 362 | first reading |
20 posts held, back to 15 August 2022 — 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 2024. An engagement rate over an empty window would be a number about nothing.
103 reactions across 12 posts, in 6 distinct kinds. The most used accounts for 45.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 47 | 45.6% | |
| 🔥 | 23 | 22.3% | |
| 👀 | 14 | 13.6% | |
| 👍 | 14 | 13.6% | |
| 🥰 | 4 | 3.88% | |
| 👎 | 1 | 0.971% |
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 14 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 103 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 15 August 2022 to 17 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
context: was in the previous launch, that went abit awry, held all my tokens and decided to get in touch with the team. ended up having a few chats with them and doing some research on the background of the project and what went wrong etc, felt like it was a bit of a web2 team trying to crack into web3 for the first time, and from what i see, they spent most of their money to push it, wasn't an extractive coin at all…
❤12👍3
I'll add some context below why i think it's good, and prefacing that it's not sponsored or w/e just in case
❤9
https://www.dextools.io/app/en/ether/pair-explorer/0xb2a1ca2219131bbf901d0711acbdd6d05e3e80f2?t=1729205179303 5.3mil $0.053 https://x.com/QuDefi_QuLabs https://www.qulabs.io/
❤20🔥4🥰3
Sticker, posted without a caption
❤3🥰1
Looking forward to something tomorrow
👀12🔥7❤3
Well, that's a bear market for ya lads.
Video, posted without a caption
Presale was not hard to get into and the chart is sittin' decently well. At least high up enough that you can take your initials and let the vesting come through at will. Chart
🔥3👎1
Also, comments should be available now. If I see some interesting stuff, I'll be sharing them here more often.
https://t.me/TheBNBTurtle www.twitter.com/TheBNBTurtle https://thebnbturtle.com/presale/ 30 minutes for public presale, 60 BUSD a spot. The team seems rather experienced, starting marketcap at launch will be around 40K, so you can decide to go in there also. Give it a check.
🔥4
Got something interesting in a sec.
🔥3👀2👍1
Why play alts when you can just do this?
Showing the 12 most recent of 20 posts we hold for @WAGMIVillage. 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.
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.
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 29 August 2026 — this entry's latest reading, not the date you are reading this.
“WAGMI Village” (@WAGMIVillage), 360 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/WAGMIVillage.
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.