Telegram RegisterThe public register of Telegram
Telegram profile photo for Nobar1 Update

Channel

Nobar1 Update

@Nobar1live

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

35subscribers

-5 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1003744121297
TypeChannel
Username@Nobar1live
Created13 March 2026 — measured — dated from the channel’s first post
First recorded10 August 2026
Last confirmed live17 November 2026
Measurements held7
Confirmed unchanged2 times, most recently 17 November 2026
On Telegramt.me/Nobar1live

Topic

Software piracy — 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 56% 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 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.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@Golivebola1/8516 Jun 2026, 18:15 UTC@Nobar1live/13 · this entry16 Jun 2026, 18:17 UTC1.002 minutes
@Golivebola1/8719 Jun 2026, 18:59 UTC@Nobar1live/16 · this entry19 Jun 2026, 18:59 UTC1.00under a minute
@Golivebola1/8921 Jun 2026, 11:08 UTC@Nobar1live/18 · this entry21 Jun 2026, 11:08 UTC1.00under a minute
@Golivebola1/9022 Jun 2026, 10:09 UTC@Nobar1live/19 · this entry22 Jun 2026, 10:09 UTC1.00under a minute
@Golivebola1/9224 Jun 2026, 05:26 UTC@Nobar1live/21 · this entry24 Jun 2026, 05:26 UTC1.00under a minute
@Golivebola1/9326 Jun 2026, 05:29 UTC@Nobar1live/22 · this entry26 Jun 2026, 05:30 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
@Golivebola111 (8/8 hand-verifiable sample passed)1.00under a minute@Golivebola1 (8–3)

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 11 comparable posts for this entry, running 16 June 2026 to 29 June 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 2 channels, the one whose matching posts we hold earliest is @Golivebola1. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, 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 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.

Growth

354037.59 August 2026 — 40 subscribers10 August 2026 — 40 subscribers1 September 2026 — 39 subscribers11 September 2026 — 38 subscribers7 October 2026 — 37 subscribers30 October 2026 — 36 subscribers6 November 2026 — 35 subscribers9 August 20266 November 2026
7 measurements spanning 90 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 34–41 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Nov 2026, 21:2535-1
30 Oct 2026, 14:3736-1
7 Oct 2026, 16:1837-1
11 Sept 2026, 05:0038-1
1 Sept 2026, 11:0739-1
10 Aug 2026, 19:4540no change
9 Aug 2026, 04:1540first reading

Engagement

18 posts held, back to 13 March 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 18 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Jul 2026, 11:04 UTCviews —

Nobar1 Update pinned «UPDATE AKSES WEBSITE NOBAR1 LINK WEBISTE AKTIF : https://twet.net/nobar1»

2 Jul 2026, 11:03 UTC125 viewsread 10 August 2026

UPDATE AKSES WEBSITE NOBAR1 LINK WEBISTE AKTIF : https://twet.net/nobar1

29 Jun 2026, 08:45 UTC273 viewsread 10 August 2026

MATCH : WORLD CUP TANGGAL : 30 JUNI 2026 SITUS LIVE : https://nobar1.live KOMUNITAS : @NobarSatu PREDIKSI : https://twet.net/prediksi BRASIL 🆚 JAPAN 00:00 WIB JERMAN 🆚 PARAGUAY 03:30 WIB BELANDA 🆚 MAROKO 08:00 WIB

28 Jun 2026, 10:51 UTC147 viewsread 10 August 2026

⚽️ JADWAL WORLD CUP ⚽️ 📆 29 JUNI 2026 📌 SITUS LIVE : https://nobar1.live 📢 KOMUNITAS : @NobarSatu 🎖 AFRIKA SELATAN VS KANADA ⏰ JAM 02:00 WIB

27 Jun 2026, 13:07 UTC141 viewsread 10 August 2026

⚽️ JADWAL WORLD CUP ⚽️ 📆 28 JUNI 2026 📌 SITUS LIVE : https://nobar1.live 📢 KOMUNITAS : @NobarSatu 🎖 PANAMA VS INGGRIS ⏰ JAM 04:00 WIB 🎖 KROASIA VS GHANA ⏰ JAM 04:00 WIB 🎖 KOLOMBIA VS PORTUGAL ⏰ JAM 06:30 WIB 🎖 RD KONGO VS UZBEKISTAN ⏰ JAM 06:30 WIB 🎖 ALJAZAIR VS AUSTRIA ⏰ JAM 09:00 WIB 🎖 YORDANIA VS ARGENTINA ⏰ JAM 09:00 WIB

26 Jun 2026, 05:30 UTC91 viewsread 10 August 2026

⚽️ JADWAL WORLD CUP ⚽️ 📆 27 JUNI 2026 📌 SITUS LIVE : https://nobar1.live 📢 KOMUNITAS : @NobarSatu 🎖 NORWEGIA VS PRANCIS ⏰ JAM 02:00 WIB 🎖 SENEGAL VS IRAK ⏰ JAM 02:00 WIB 🎖 TANJUNG VERDE VS ARAB SAUDI ⏰ JAM 07:00 WIB 🎖 URUGUAY VS SPANYOL ⏰ JAM 07:00 WIB 🎖 SELANDIA BARU S VS BELGIA ⏰ JAM 10:00 WIB 🎖 MESIR VS IRAN ⏰ JAM 10:00 WIB

24 Jun 2026, 05:26 UTC72 viewsread 10 August 2026

⚽️ JADWAL WORLD CUP ⚽️ 📆 25 JUNI 2026 📌 SITUS LIVE : https://nobar1.live 📢 KOMUNITAS : @NobarSatu 🎖 SWISS VS KANADA ⏰ JAM 02:00 WIB 🎖 BOSNIA VS QATAR ⏰ JAM 02:00 WIB 🎖 MAROKO VS HAITI ⏰ JAM 05:00 WIB 🎖 SKOTLANDIA VS BRAZIL ⏰ JAM 05:00 WIB 🎖 AFRIKA S VS KOREA S ⏰ JAM 08:00 WIB 🎖 CEKO VS MEKSIKO ⏰ JAM 08:00 WIB

22 Jun 2026, 19:16 UTC83 viewsread 10 August 2026

Daftar akun di nobar1 agar bisa mengirim pesan di live chat. https://nobar1.live/register

22 Jun 2026, 10:09 UTC74 viewsread 10 August 2026

⚽️ JADWAL WORLD CUP ⚽️ 📆 23 JUNI 2026 📌 SITUS LIVE : https://nobar1.live 📢 KOMUNITAS : @NobarSatu 🎖 ARGENTINA VS AUSTRIA ⏰ JAM 00:00 WIB 🎖 PRANCIS VS IRAK ⏰ JAM 04:00 WIB 🎖 NORWEGIA VS SENEGAL ⏰ JAM 07:00 WIB 🎖 YORDANIA VS ALJAZAIR ⏰ JAM 10:00 WIB

21 Jun 2026, 11:08 UTC55 viewsread 10 August 2026

⚽️ JADWAL WORLD CUP ⚽️ 📆 22 JUNI 2026 📌 SITUS LIVE : https://nobar1.live 📢 KOMUNITAS : @NobarSatu 🎖 BELGIA VS IRAN ⏰ JAM 02:00 WIB 🎖 URUGUAY VS TANJUNG VERDE ⏰ JAM 05:00 WIB 🎖 SELANDIA BARU VS MESIR ⏰ JAM 08:00 WIB

20 Jun 2026, 10:04 UTC49 viewsread 10 August 2026

⚽️ JADWAL WORLD CUP ⚽️ 📆 21 JUNI 2026 📌 SITUS LIVE : https://nobar1.live 📢 KOMUNITAS : @NobarSatu 🎖 BELANDA VS SWEDIA ⏰ JAM 00:00 WIB 🎖 JERMAN VS PANTAI GADING ⏰ JAM 03:00 WIB 🎖 EKUADOR VS CURACAO ⏰ JAM 07:00 WIB 🎖 TUNISIA VS JEPANG ⏰ JAM 11:00 WIB 🎖 SPANYOL VS ARAB SAUDI ⏰ JAM 23:00 WIB

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

Named by 1 registered channel — 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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“Nobar1 Update” (@Nobar1live), 35 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/Nobar1live.

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.