Telegram RegisterThe public register of Telegram

Channel

BABY | PORTAL

@baby_token_sol

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

2,748subscribers

-5 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-1002040713252
TypeChannel
Username@baby_token_sol
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/baby_token_sol

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 11 August 2026 and assigned it the closest of 31 fixed categories, at 77% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@wulfy_sol/42516 Jan 2025, 15:32 UTC@baby_token_sol/946 · this entry16 Jan 2025, 15:32 UTC1.00under a minute
@wulfy_sol/42616 Jan 2025, 17:03 UTC@baby_token_sol/947 · this entry16 Jan 2025, 17:03 UTC1.00under a minute
@wulfy_sol/42917 Jan 2025, 17:03 UTC@baby_token_sol/949 · this entry17 Jan 2025, 17:03 UTC1.00under a minute
@wulfy_sol/43018 Jan 2025, 17:01 UTC@baby_token_sol/950 · this entry18 Jan 2025, 17:01 UTC1.00under a minute
@wulfy_sol/43221 Jan 2025, 14:25 UTC@baby_token_sol/952 · this entry21 Jan 2025, 14:25 UTC1.00under a minute
@wulfy_sol/43321 Jan 2025, 17:07 UTC@baby_token_sol/953 · this entry21 Jan 2025, 17:07 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@wulfy_sol11 (8/8 hand-verifiable sample passed)1.00under a minute@wulfy_sol (92)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 9 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 13 January 2025 to 19 July 2025. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Across the whole group of 2, the earliest publisher we hold is @wulfy_sol. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

2,7482,7532,750.57 August 2026 — 2,753 subscribers7 August 2026 — 2,753 subscribers10 August 2026 — 2,748 subscribers7 August 202610 August 2026
3 measurements spanning 4 days, net -5. 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 2,747–2,754 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 19:512,748-5
7 Aug 2026, 20:272,753no change
7 Aug 2026, 02:302,753first reading

Engagement

20 posts held, back to 13 January 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 19 July 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3s
Average length
3s

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

111 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 41.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4641.4%
3632.4%
👍2926.1%

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 20 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 111reactions 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 January 2025 to 19 July 2025, 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

19 Jul 2025, 22:01 UTC≈2,620 views15 reactionsread 7 August 2026
Video

WULFY RT @baby_sol_2: $BABY2 | SOL | Presale Introducing BABY2, the ultimate leader of all MEME's! 🚀 Deluge trending, strong community vibes, epic hype raids, and a prebooked marketing blitz. NO whitelist, NO jeet call groups—just pure, unstoppable hype! Backed by @atemcalls Last projects: #Grokheroes 7x #WULFY 10x #SafeMars 16x #Blackrock 21x #PokeGrok 42x #BABY 420x 👉 Start: july 21 | 3pm UTC 👉 End: july 23 |

8🔥4👍3

2 Apr 2025, 05:04 UTC≈3,320 views7 reactionsread 7 August 2026

WULFY RT @saul_pink: Stoopid Cats raised over $100,000 with us at @pinkecosystem last week giving testament to what a team can achieve with a competent marketing plan and drive! What sales are you interested in this week on Pinksale? tweet

4🔥2👍1

26 Jan 2025, 18:08 UTC≈4,910 views4 reactionsread 7 August 2026
Photo

WULFY JUST IN: $WULFY AMA WITH ELITE CRYPTO LOUNGE at 6PM UTC - 👉🏽 You can buy $WULFY here: https://t.co/tN0loBLBHJ 📈 CA: 6Qn2muot6pbTTWJ6F83zrpBQTFjb69FcmG1xbg64RoUD - #WUUUU https://t.co/N7hfDSmF8V tweet

👍2🔥2

24 Jan 2025, 17:06 UTC≈3,720 views2 reactionsread 7 August 2026
Photo

WULFY JUST IN: $WULFY AMA WITH SONIC WHALES at 6PM UTC - 👉🏽 You can buy $WULFY here: https://t.co/tN0loBLBHJ 📈 CA: 6Qn2muot6pbTTWJ6F83zrpBQTFjb69FcmG1xbg64RoUD - #WUUUU https://t.co/xyVqV1UXH6 tweet

🔥2

23 Jan 2025, 04:23 UTC≈3,080 views3 reactionsread 7 August 2026

WULFY ANNOUNCEMENT VESTING RELEASE Dear Wulfy Family, As you know, we have successfully migrated $BABY and $LEGEND holders into $WULFY. The initial plan was to distribute the migrated tokens in stages, based on specific milestones. Migration Token Vesting Schedule: - 20% released after 2 weeks - 20% released at $10M MC - 20% released at $50M MC - 20% released at $100M MC - 20% released at $500M MC We already tri

🔥3

21 Jan 2025, 17:07 UTC≈1,850 views7 reactionsread 7 August 2026
Photo

WULFY JUST IN: $WULFY AMA WITH BRAVE LOUNGE at 6PM UTC - 👉🏽 You can buy $WULFY here: https://t.co/tN0loBLBHJ 📈 CA: 6Qn2muot6pbTTWJ6F83zrpBQTFjb69FcmG1xbg64RoUD - #WUUUU https://t.co/O4oF4epLjF tweet

🔥32👍2

21 Jan 2025, 14:25 UTC≈1,730 views2 reactionsread 7 August 2026

WULFY Thank you to all our supporters! We've faced challenging times and stood strong during difficulties. Despite ongoing paid FUD attacks against us and an organized selloff event by a former core team member from our previous project ($BABY), we remain resilient. Meanwhile, $TRUMP and $MELANIA have drained liquidity from weaker projects, but we continue to push forward together. - 👉🏽 buy $WULFY here: https://t.co/

1👍1

20 Jan 2025, 17:07 UTC≈1,570 views4 reactionsread 7 August 2026
Photo

WULFY JUST IN: $WULFY AMA WITH MANAGER CALLING at 6PM UTC - 👉🏽 You can buy $WULFY here: https://t.co/tN0loBLBHJ 📈 CA: 6Qn2muot6pbTTWJ6F83zrpBQTFjb69FcmG1xbg64RoUD - #WUUUU https://t.co/GN2geRI160 tweet

🔥31

18 Jan 2025, 17:01 UTC≈1,620 views4 reactionsread 7 August 2026
Photo

WULFY JUST IN: $WULFY AMA WITH FUTURE LOUNGE at 6PM UTC - 👉🏽 You can buy $WULFY here: https://t.co/tN0loBLBHJ 📈 CA: 6Qn2muot6pbTTWJ6F83zrpBQTFjb69FcmG1xbg64RoUD - #WUUUU https://t.co/tlBTCKDdJk tweet

🔥21👍1

17 Jan 2025, 17:03 UTC≈1,430 views3 reactionsread 7 August 2026
Photo

WULFY JUST IN: $WULFY AMA WITH XDC PRIVATE at 6PM UTC - 👉🏽 You can buy $WULFY here: https://t.co/tN0loBLBHJ 📈 CA: 6Qn2muot6pbTTWJ6F83zrpBQTFjb69FcmG1xbg64RoUD - #WUUUU https://t.co/sGiW6VnEvF tweet

🔥3

16 Jan 2025, 19:50 UTC≈1,370 views7 reactionsread 7 August 2026
Photo

WULFY RT @cryptokray2: @MrBeast Most liked reply wins? Let’s go. 🐺 If the $WULFY FAM wins this, everything goes straight to our $WULFY community. WULFY isn’t just a community—it’s the future. https://t.co/SLGEsWie5c @WULFY_SOL @MrBeast love the $WULFY HAT! Let’s go! https://t.co/BSN17Pvt9Y tweet

3👍2🔥2

16 Jan 2025, 17:03 UTC≈1,230 views3 reactionsread 7 August 2026
Photo

WULFY JUST IN: $WULFY AMA WITH SOLITAIRE at 6PM UTC - 👉🏽 You can buy $WULFY here: https://t.co/tN0loBLBHJ 📈 CA: 6Qn2muot6pbTTWJ6F83zrpBQTFjb69FcmG1xbg64RoUD - #WUUUU https://t.co/Nhmwogq6Pi tweet

1👍1🔥1

Showing the 12 most recent of 20 posts we hold for @baby_token_sol. 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.

Citation-graph rank

Citation-graph rank — 199,723 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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.

Mentions

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.

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“BABY | PORTAL” (@baby_token_sol), 2,748 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/baby_token_sol.

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.