Telegram RegisterThe public register of Telegram
Telegram profile photo for Lupi Team

Channel

Lupi Team

@LupiTeam

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

8,303subscribers

+125 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001084059613
TypeChannel
Username@LupiTeam
DescriptionTeam di traduzione italiano di One Piece, Dragon Ball, OnePunch Man, Hunter X Hunter, Berserk e tanti altri Manga! Sito: https://lupiteam.net/ Contatti: @LupiTeam_Bot
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/LupiTeam

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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.

Growth

8,1788,3078,242.56 August 2026 — 8,178 subscribers7 August 2026 — 8,183 subscribers10 August 2026 — 8,190 subscribers14 August 2026 — 8,193 subscribers17 August 2026 — 8,194 subscribers20 August 2026 — 8,197 subscribers24 August 2026 — 8,213 subscribers27 August 2026 — 8,224 subscribers29 August 2026 — 8,228 subscribers6 September 2026 — 8,244 subscribers11 September 2026 — 8,247 subscribers14 September 2026 — 8,260 subscribers18 September 2026 — 8,263 subscribers28 September 2026 — 8,279 subscribers9 October 2026 — 8,292 subscribers14 October 2026 — 8,300 subscribers17 October 2026 — 8,299 subscribers20 October 2026 — 8,303 subscribers23 October 2026 — 8,302 subscribers26 October 2026 — 8,307 subscribers29 October 2026 — 8,306 subscribers31 October 2026 — 8,304 subscribers4 November 2026 — 8,303 subscribers8,3036 August 20264 November 2026
23 measurements spanning 89 days, net +125. 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 8,159–8,326 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 23
Measured (UTC)SubscribersChange
4 Nov 2026, 04:308,303-1
31 Oct 2026, 20:268,304-2
29 Oct 2026, 04:318,306-1
26 Oct 2026, 11:158,307+5
23 Oct 2026, 10:468,302-1
20 Oct 2026, 19:288,303+4
17 Oct 2026, 09:098,299-1
14 Oct 2026, 00:048,300+8
9 Oct 2026, 06:178,292+13
28 Sept 2026, 10:598,279+16
18 Sept 2026, 15:008,263+3
14 Sept 2026, 14:018,260+13
11 Sept 2026, 07:598,247+3
6 Sept 2026, 20:218,244+16
29 Aug 2026, 18:048,228+4
27 Aug 2026, 03:368,224+11
24 Aug 2026, 05:358,213+16
20 Aug 2026, 12:248,197+3
17 Aug 2026, 10:388,194+1
14 Aug 2026, 00:468,193first reading

Engagement

44 posts held, back to 31 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 26 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
74.8%
avg views ÷ 8,303 subscribers
Avg views / post
6,210
7 posts measured
Reaction rate
1.68%
reactions ÷ views · ER floor
Posts in window
7
of 44 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 30 October 2026
Posts held44 (31 May 2026 – 30 October 2026)
Views total43,470
Reactions total730
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 11:11 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
48
Videos
3
Links
915

Lifetime counters from Telegram’s own channel header, read 5 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

3,193 reactions across 34 posts, in 28 distinct kinds. The most used accounts for 71.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2,27071.1%
🔥51116.0%
👍1123.51%
🍌782.44%
👏361.13%
😱341.06%
🤣300.94%
😨210.658%
❤‍🔥170.532%
😍120.376%
💯100.313%
🐳90.282%
🤔60.188%
🥰60.188%
👻50.157%
🤬50.157%
⚡40.125%
🙏40.125%
🤯40.125%
🦄40.125%
8 further kinds150.47%

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 34 of the 44 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 3,193 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 44 most recent posts we hold, published 31 May 2026 to 30 October 2026, 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

Telegram’s own ‘edited’ marker: 1 of 7 posts held from the last 30 days (14.3%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

30 Oct 2026, 22:48 UTC≈3,630 views98 reactionsread 5 November 2026

30 km a piedi dopo e con sole due ore di sonno in corpo, finalmente ci siamo. Il capitolo 1197 è pronto per essere letto! Ci vediamo in giro per Lucca per tutto il weekend! P.S. Per rispondere alle vostre scorse domande: no, non abbiamo organizzato raduni durante la fiera. Ma se mi vedete in giro, fermatemi pure per un saluto! -Cap

❤86🔥6🥰3🍌2👏1

30 Oct 2026, 22:44 UTC≈3,950 views128 reactionsread 5 November 2026

Disponibile⁣ il capitolo 1197 - L'amore è difesa di One Piece Deluxe. #OnePieceDeluxe

❤98🔥26🍌4

30 Oct 2026, 07:05 UTC≈4,150 views134 reactionsread 5 November 2026

Buongiorno direttamente da Lucca! Abbiamo già pronte le traduzioni e a breve partiamo con l'editing. Farò revisione di tutto in coda tra un padiglione e l'altro, connessione permettendo, quindi ancora un po' di pazienza! -Cap

❤104🔥20👍7🥰3

18 Oct 2026, 01:45 UTC≈7,660 views88 reactionsread 5 November 2026

Se il buongiorno si vede dal mattino (o dalla notte, per chi ha fatto serata), allora lo sarà dopo questo delivery notturno del capitolo 1196, in versione STANDARD! Purtroppo anche a questo giro niente raw, quindi abbiamo come di consueto utilizzato una fonte inglese più affidabile di TCB. Poi settimana prossima arriva l'hard disk nuovo al nostro editor del venerdì quindi riusciremo sia a recuperare le vecchie DELUXE…

❤79🔥6🍌3

18 Oct 2026, 01:44 UTC≈7,050 views95 reactionsread 5 November 2026

Disponibile⁣ il capitolo 1196 - L’amore di chi brama la morte non ha alcun valore di One Piece Deluxe. #OnePieceDeluxe

❤76🔥12🗿2🦄2🍌1👏1💯1

10 Oct 2026, 15:35 UTC≈8,960 views93 reactionsread 5 November 2026

Capitolo 1195 per voi, al momento in versione STANDARD! Stiamo andando un po' a rilento nelle ultime settimane, come avrete notato, perché uno dei nostri editor ha bruciato il disco fisso e fino a fine mese è senza attrezzatura. Pazientate ancora un pochino! 🙏 Buona lettura! -Cap

❤75❤‍🔥6🔥5🍌3👍2💯2

10 Oct 2026, 15:34 UTC≈8,070 views94 reactionsread 5 November 2026

Disponibile⁣ il capitolo 1195 - Debolezza di One Piece Deluxe. #OnePieceDeluxe

🔥64❤27🍌3

27 Sept 2026, 06:33 UTCviews —

Lupi Team pinned «Disponibile⁣ il capitolo 1194 - Tutto muta di One Piece Deluxe. #OnePieceDeluxe»

26 Sept 2026, 22:35 UTC≈10,800 views22 reactionsread 5 November 2026

Leggo ora il capitolo 1194 in diretta su twitch.tv/sdrchannel Vi aspetto! 🫶🏼 -Cap

❤22

26 Sept 2026, 20:28 UTC≈9,730 views82 reactionsread 5 November 2026

Questa settimana le scan sono uscite un giorno in ritardo, ma in compenso ieri sono uscite le raw per intero! Quindi finalmente torniamo a pubblicare direttamente la DELUXE col capitolo 1194! Buona lettura! -Cap

❤69🔥11🍌2

26 Sept 2026, 20:28 UTC≈9,380 views106 reactionsread 5 November 2026

Disponibile⁣ il capitolo 1194 - Tutto muta di One Piece Deluxe. #OnePieceDeluxe

❤88🔥14🍌4

13 Sept 2026, 14:15 UTCviews —

Lupi Team pinned «Disponibile⁣ il capitolo 1193 - Sto ancora facendo pratica di One Piece Deluxe. #OnePieceDeluxe»

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Lupi Team” (@LupiTeam), 8,303 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/LupiTeam.

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.