Channel
@UlvensChannel
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
28subscribers
-2 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001397022765 |
|---|---|
| Type | Channel |
| Username | @UlvensChannel |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 8 times, most recently 9 November 2026 |
| On Telegram | t.me/UlvensChannel |
Other / unclassifiable — 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 30 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 the other topics.
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.
Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @UlvensChannel/108 · this entry29 Nov 2023, 19:02 UTC | @UlvensMemes/229329 Nov 2023, 19:03 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @UlvensMemes | 6 (6/6 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (4–2) |
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 0 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 11 comparable posts for this entry, running 12 May 2023 to 14 March 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @UlvensMemes. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 11 November 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.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 10:56 | 28 | -1 |
| 24 Aug 2026, 14:33 | 29 | -1 |
| 11 Aug 2026, 03:45 | 30 | no change |
| 9 Aug 2026, 07:45 | 30 | first reading |
20 posts held, back to 15 April 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 March 2025. An engagement rate over an empty window would be a number about nothing.
The owner of this channel has been inactive for the last 18 months. If they remain inactive for the next 7 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
You can leave this channel safely, by the way, the new channel will be used from now on... Talk soon! Remember, my new account: @A_Star_Ulven My new channel: https://t.me/A_Star_Ulven_channel Will probably not remake all channels at once, so if you subscribe you can stay up to date with new channels and groups I make.
Since I lost ownership of my other channels and groups, time to restart everything I guess... Here we go. Join my new channel! https://t.me/A_Star_Ulven_channel
Please feel free to add @A_Star_Ulven to any groups I used to be in. I have temporarily enabled groups and channel invites. If that doesn't work, you can also send me a link.
OK. New account: @A_Star_Ulven
I thought I'd be creating the new Ulven account today but there has been an issue which means it will be delayed again. I expect two more weeks. Maybe more. I will return when I can get those new SIMs. I am not going to sign up to a VoIP number because then I have this problem all over again.
I should clarify these channels are lost permanently due to the way Telegram handles groups and channels. All groups and channels are lost permanently save for the ones I have appointed admins to: they can ban and kick but not appoint additional admins or change the ownership of these. So I will have to recreate all my groups and chats. I know it's a hassle, I'll let you know when I'm done and share the links here a…
Expect to see me coming back around the end of October / beginning of November on a new Telegram account. I will publish the new username here. This all came at a really unfortunate point in my life when I have been extraordinarily busy, that is why it took me so long, which on the other hand has been quite positive as it allowed me to focus away from the hundred Telegram groups I was in.
I also recommend deleting PMs from both ends because it is possible whoever logs into my account would leak private messages.
This is what happened, when I sent the link inside this pastebin, my account got logged off from every single device I have. To be clear, the pastebin link I shared is not the problem. The problem is the link inside this pastebin. It's a NYT article with a bunch of tracking garbage, and I think that tripped the anti spam system I will stop posting memes for a while.
As I announced on the memes channel, my Ulven account @AlgorithmWolf was permanently lost. I have contacted support, but they are unresponsive and I assume the account will be deleted when the inactivity timer expires. I know it is not deleted, but I am unable to access it. I do not have other accounts at the moment, so if anyone contacts you claiming to be Ulven, it is an impostor. I am thinking about my next step…
Aquí!
Showing the 12 most recent of 20 posts we hold for @UlvensChannel. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
@UlvensChannel named 2 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.
References a handle that is not a live channel — we have no record it ever was one.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“A* Ulven’s Channel” (@UlvensChannel), 28 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/UlvensChannel.
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.