Telegram RegisterThe public register of Telegram
Telegram profile photo for Lu3ky13

Channel

Lu3ky13

@lu3ky_13

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

3,008subscribers

+21 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-1002167263767
TypeChannel
Username@lu3ky_13
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live27 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/lu3ky_13

Growth

2,9833,0082,995.57 August 2026 — 2,987 subscribers7 August 2026 — 2,987 subscribers8 August 2026 — 2,986 subscribers11 August 2026 — 2,983 subscribers14 August 2026 — 2,991 subscribers17 August 2026 — 2,993 subscribers21 August 2026 — 2,999 subscribers24 August 2026 — 3,006 subscribers27 August 2026 — 3,008 subscribers7 August 202627 August 2026
9 measurements spanning 20 days, net +21. 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,979–3,012 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 19:483,008+2
24 Aug 2026, 12:273,006+7
21 Aug 2026, 01:052,999+6
17 Aug 2026, 16:352,993+2
14 Aug 2026, 12:282,991+8
11 Aug 2026, 05:272,983-3
8 Aug 2026, 03:362,986-1
7 Aug 2026, 18:332,987no change
7 Aug 2026, 18:212,987first reading

Engagement

18 posts held, back to 24 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 28 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

8 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
450.0%
🔥450.0%

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 5 of the 18 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 8reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 24 July 2026 to 28 July 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

28 Jul 2026, 13:01 UTC352 viewsread 7 August 2026

Testing gRPC-Web APIs? Binary protobuf = pain in Burp 😤 Built a Burp extension that: → Decodes protobuf → JSON → Edit any field → Auto re-encodes on send → Works without .proto files IDOR hunting on modern apps just got easier. https://github.com/Lu3ky13/gRPC-Web-Burp-Repeater

28 Jul 2026, 12:57 UTC277 viewsread 7 August 2026

🚀 Released: gRPC-Web Burp Repeater Decode, edit & replay gRPC-Web protobuf traffic in Burp Suite. ✅ Auto decode/encode ✅ Edit JSON, not binary ✅ No schema needed ✅ Full repeater functionality Perfect for bug bounty on modern APIs. 🔗 https://github.com/Lu3ky13/gRPC-Web-Burp-Repeater #BugBounty

28 Jul 2026, 12:17 UTC271 viewsread 7 August 2026
Photo

wtf accepted new Version 3.1 download here https://addons.mozilla.org/en-US/firefox/addon/js-deep-scraper-pro/

28 Jul 2026, 12:11 UTC283 views1 reactionsread 7 August 2026

new Version coming soon one click crawling all web https://addons.mozilla.org/en-US/firefox/addon/js-deep-scraper-pro/

1

28 Jul 2026, 11:38 UTC306 views3 reactionsread 7 August 2026

running #Kimi #K3 locally need $235,000–$370,000 8× NVIDIA H100 GPUs $200,000–$280,000 Server (CPU, RAM, motherboard, storage, networking) $30,000–$70,000 Rack, UPS, switches $5,000–$20,000 Total purchase $235,000–$370,000

🔥21

27 Jul 2026, 21:39 UTC350 views1 reactionsread 7 August 2026
Photo

i used Antigravity to crack http debugger

1

26 Jul 2026, 18:30 UTC398 viewsread 7 August 2026
Photo

This new model is now free to try, just create an account and you can use it. This model may be available for a while. We want your feedback Depending on the response and usage, you may see some slowdown in usage because we expect over 5,000 people to use it after the post Create an account and try it now. We look forward to your feedback https://obsidianlabs.cloud

26 Jul 2026, 17:44 UTC378 views2 reactionsread 7 August 2026

🚀 New module release on Obsidian Labs! We’ve just shipped 4 new active tools to simplify your offensive workflow: 1️⃣ Hash Identifier 2️⃣ SQLi Payload Generator 3️⃣ SSRF / XXE Generator 4️⃣ Targeted Wordlist Generator https://obsidianlabs.cloud

1🔥1

Showing the 12 most recent of 18 posts we hold for @lu3ky_13. 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 — 72,647 of 1,626,935entries 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

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

The Bug Bounty Hunter
@thebugbountyhunter · 50,140
Telegram ranks this channel #29 of 60 here — alongside 59 others — read 25 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Lu3ky13” (@lu3ky_13), 3,008 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/lu3ky_13.

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.