7 Oct 2022, 19:35 UTC≈3,970 viewsread 7 August 2026
Today marks the release of the beta of Metacurse, find the link to download at the link below. https://medium.com/@yarloo/metacurse-beta-release-ef37e384ff62
Channel
Yarloo Announcements
@yarlannouncements
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
2,802subscribers
-30 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001247942845 |
|---|---|
| Type | Channel |
| Username | @yarlannouncements |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/yarlannouncements |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 11:18 | 2,802 | -2 |
| 29 Aug 2026, 05:12 | 2,804 | -2 |
| 26 Aug 2026, 04:33 | 2,806 | -1 |
| 22 Aug 2026, 23:52 | 2,807 | -2 |
| 19 Aug 2026, 23:51 | 2,809 | -11 |
| 16 Aug 2026, 18:55 | 2,820 | -2 |
| 13 Aug 2026, 14:27 | 2,822 | -5 |
| 10 Aug 2026, 10:45 | 2,827 | -5 |
| 7 Aug 2026, 04:06 | 2,832 | no change |
| 7 Aug 2026, 01:47 | 2,832 | first reading |
Engagement
20 posts held, back to 10 May 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 2 pages 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 7 October 2022. An engagement rate over an empty window would be a number about nothing.
Recent posts
4 Oct 2022, 13:00 UTC≈3,890 viewsread 7 August 2026
We know that we've been rather silent for the past few weeks, but our silence ends now. We're super excited to share with you that Metacurse, developed by Wopp.io and Jesper (Project Lead) (@tharanios), is finally coming out for beta testing and QA feedback collection on October 7th. In case of any bugs you encounter, please report it via the form below and our development partners will take care of it. https://fo…
22 Aug 2022, 12:00 UTC≈3,040 viewsread 7 August 2026
Ahoy, me hearties! 👋 We're incredibly excited to share with you the KYC form for Metacurse's beta! We'd also like to inform you that Metacurse will go through 3 different testing stages with the community, which we'll announce in a news video to better elaborate the state of the game. Here's the link: https://forms.gle/33d7ahFiUFupNW2w9
8 Aug 2022, 15:12 UTC≈2,830 viewsread 7 August 2026
Extra annoucement: 🗣 We're very happy to see the response towards the imminent launch of Metacurse's beta, but we STRONGLY advise you all not to make any YARL purchases until further notice from our side. The reason we recommend so is due to extremely low liquidity in the YARL/BUSD pair, and we've been working on a solution for the past 2 months and are close to unveiling it. For now, enjoy Metacurse when we do la…
8 Aug 2022, 12:34 UTC≈2,210 viewsread 7 August 2026
Hello, seafarers! 👋 As promised, we said we had a major announcement to make, and it's a rather important one. We'd like to inform everyone that Metacurse has finally been wrapped up. We're currently in the process of adding the last touches to the first playable version which we'll share with our community shortly for playtesting and bug reporting. The version we'll release is Beta 0.9 - and we will be doing…
22 Jun 2022, 13:15 UTC≈2,170 viewsread 7 August 2026
It's a slow week, but the upcoming event will be the largest event we ever set up. The event is intended to bring in non-crypto gamers into the Metacurse game! 🎲 So here is the update for Wednesday (22-06) __________________________________________________________ Update status for the community 🏴☠️ : 1. Treasure hunt event inbound. 2. Weekly update campaign initiated. (Wednesdays and Fridays) Keep an eye…
18 Jun 2022, 21:21 UTC≈2,070 viewsread 7 August 2026
https://www.youtube.com/watch?v=2DetBE4pxQ8&ab_channel=YarlooEntertainment
18 Jun 2022, 21:21 UTC≈1,720 viewsread 7 August 2026
https://twitter.com/Yarloo_RST/status/1538270576393043968
16 Jun 2022, 08:52 UTC≈1,590 viewsread 7 August 2026
Update status for the community 🏴☠️ : 1. Kickstarting of Yarloo's weekly update campaign on both Wednesdays and Fridays starting from the last week of June. 2. Upcoming video update from Yarloo to discuss the past and the future. 3. Preparations for AMA & special treasure hunt event ongoing.
8 Jun 2022, 08:33 UTC≈1,630 viewsread 7 August 2026
https://twitter.com/Yarloo_RST/status/1534452690687823873
7 Jun 2022, 13:30 UTC≈1,410 viewsread 7 August 2026
https://twitter.com/Yarloo_RST/status/1534165849149526016?t=APdMkCigfEt6xRRDTewHrQ&s=19
4 Jun 2022, 18:08 UTC≈2,370 viewsread 7 August 2026
AMA ANNOUNCEMENT - METACURSE (BY YARLOO) - 75 MINUTES Alright Apes, got a few things going on IRL this weekend so keeping it quiet, just the one AMA today - we have the team from Yarloo joining us to talk about the upcoming release of their P2E 2.0 game Metacurse which is set to debut next month - they are active already on BSC wanted to give people a chance to learn more about their game and growing ecosystem - htt…
Showing the 12 most recent of 20 posts we hold for @yarlannouncements. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- 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
- 1
- vacant every time we have ever looked
@yarlannouncements named 1 handle 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.
@tharanios
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“Yarloo Announcements” (@yarlannouncements), 2,802 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/yarlannouncements.
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.