Telegram RegisterThe public register of Telegram
Telegram profile photo for Null's FAQ (RU)

Channel

Null's FAQ (RU)

@nulls_russ_faq

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Polls · Cite this entry

41subscribers

-9 since we began measuring on 27 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002174299854
TypeChannel
Username@nulls_russ_faq
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live14 November 2026
Measurements held9
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/nulls_russ_faq

Topic

Gaming — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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.

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 in near-verbatim form on 4 other registered channels. This entry also sits inside a group of 5 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. 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
@dnclser_chat/799918 May 2026, 12:58 UTC@nulls_russ_faq/7980 · this entry18 May 2026, 12:58 UTC1.00under a minute
@dnclser_chat/800418 May 2026, 23:00 UTC@nulls_russ_faq/7985 · this entry18 May 2026, 23:00 UTC1.00under a minute
@dnclser_chat/800719 May 2026, 05:02 UTC@nulls_russ_faq/7988 · this entry19 May 2026, 05:02 UTC1.00under a minute
@dnclser_chat/800919 May 2026, 09:03 UTC@nulls_russ_faq/7990 · this entry19 May 2026, 09:03 UTC1.00under a minute
@dnclser_chat/801219 May 2026, 15:04 UTC@nulls_russ_faq/7993 · this entry19 May 2026, 15:04 UTC1.00under a minute
@dnclser_chat/801319 May 2026, 17:05 UTC@nulls_russ_faq/7994 · this entry19 May 2026, 17:05 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@dnclser_chat8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–0)
@nulls_ens8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–0)
@dnclservs_chat8 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (8–0)
@nulls_russ8 (8/8 hand-verifiable sample passed)1.00under a minute@nulls_russ (8–0)

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 8 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 8 comparable posts for this entry, running 18 May 2026 to 20 May 2026. 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).

Of the group of 5 channels, the one whose matching posts we hold earliest is @dnclser_chat. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_copy · 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.

Channels linked by matching posts

This channel is in a group of 5 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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.

Growth

415045.527 August 2026 — 50 subscribers27 August 2026 — 50 subscribers4 September 2026 — 47 subscribers13 September 2026 — 46 subscribers27 September 2026 — 45 subscribers7 October 2026 — 44 subscribers14 October 2026 — 43 subscribers6 November 2026 — 42 subscribers14 November 2026 — 41 subscribers27 August 202614 November 2026
9 measurements spanning 79 days, net -9. 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 40–51 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Nov 2026, 07:0041-1
6 Nov 2026, 00:5842-1
14 Oct 2026, 09:5643-1
7 Oct 2026, 13:5544-1
27 Sept 2026, 16:4145-1
13 Sept 2026, 07:3846-1
4 Sept 2026, 09:5747-3
27 Aug 2026, 15:0050no change
27 Aug 2026, 14:4650first reading

Engagement

20 posts held, back to 18 May 2026 — 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 20 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 May 2026, 01:08 UTC2 viewsread 27 August 2026

Minor server restart — implemented Squeak's gadget and star powers, fixed damage from his super attack. And also new Bea second star power. #nullsbrawl

19 May 2026, 23:07 UTC2 viewsread 27 August 2026
Photo

Null's Brawl has been updated to the latest version 35.139 with Belle and Squeak! We've decided to close Alpha testing because most of the players stopped playing standard version because of it, even though there were a lot of unimplemented things. So now battles codebase previously used in Alpha is working at standard version. What's new: 1. Belle and Squeak (not all gadgets/starpowers). 2. New gamemodes: Knockout…

19 May 2026, 21:06 UTC1 viewsread 27 August 2026

There will be short maintenance to fix some bugs and return back Big Game. Maintenance done. #nullsbrawl

19 May 2026, 17:05 UTC1 viewsread 27 August 2026
Photo

Weekend is coming. So let's see what happens with Null's Brawl update. Important: we will finish Alpha-testing of new battles implementation with this update. Now it will be used in classic server, and Null's Brawl Alpha will be closed. You won't be able to use your NBA account in classic server. Let's see what we have done: 1) Compatibility with latest version of the game 35.x and new visual content (pins, skins, …

19 May 2026, 15:04 UTC1 viewsread 27 August 2026

We did some maintenance breaks after Null's Clash update. Changes: — Fixed crashes when donating CW units — Enabled replays in legendary league and added opportunity to share them in clan — Implemented anti-spam system, that won't allow to spam emoji in clans (they could create some lags in game) — Fixed disconnects when searching for clan members and other minor bugfixes #nullsclash

19 May 2026, 09:03 UTC1 viewsread 27 August 2026
Photo

Null's Clash has been updated to the latest version 14.0.6! What's new? 1. Town Hall 14 2. New Buildings levels 3. Pets 4. All new content from the previous seasons (inc. sceneries) You can get new version from our website (https://nulls.gg/servers/nulls-clash) or from the post below. #nullsclash

19 May 2026, 05:02 UTC1 viewsread 27 August 2026

Forgot about Null's Royale updates? Let’s finally get them! There are really big changes. What’s new: — Custom cards were removed from cards collection: we got contradictory results of poll, so the thought the best future of custom cards is to make them available only in special events. They were removed from ladder because they were much unbalanced. Now you can play them in special challenge, Null’s Legacy, where yo…

19 May 2026, 03:02 UTC1 viewsread 27 August 2026
Photo

Null's Royale was updated to latest version with Mother Witch! All details in post below.

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

18 May 2026, 10:58 UTCAnonymous Poll0 voters

Btw... may be we should release next update in classic Null's Brawl and close Alpha?

  1. Agree!0%
  2. Disagree.0%
  3. I don't play Null's Brawl, I'm waiting for Royale and Clash updates!0%

Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 18 May 2026 to 20 May 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“Null's FAQ (RU)” (@nulls_russ_faq), 41 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/nulls_russ_faq.

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.