Telegram RegisterThe public register of Telegram
Telegram profile photo for Localsint

Channel

Localsint

@localsint

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

85subscribers

-12 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-1003876511415
TypeChannel
Username@localsint
Created3 July 2026 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live12 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/localsint

Topic

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 51% 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 why it has no browse page of its own yet.

Growth

8597919 August 2026 — 97 subscribers9 August 2026 — 97 subscribers17 August 2026 — 95 subscribers9 September 2026 — 93 subscribers18 September 2026 — 91 subscribers2 October 2026 — 87 subscribers12 October 2026 — 85 subscribers9 August 202612 October 2026
7 measurements spanning 64 days, net -12. 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 83–99 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 15:5185-2
2 Oct 2026, 09:1987-4
18 Sept 2026, 06:0191-2
9 Sept 2026, 09:5893-2
17 Aug 2026, 10:4695-2
9 Aug 2026, 12:0297no change
9 Aug 2026, 10:3297first reading

Engagement

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

Reaction mix

33 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤33100.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 8 of the 12 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 33 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 3 July 2026 to 13 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

13 Jul 2026, 22:59 UTC99 viewsread 9 August 2026

Whole new site being revamped more stealer logs country and many more stay tuned.

8 Jul 2026, 17:38 UTC169 views3 reactionsread 9 August 2026

Hello everyone, we have made a new project and its basically showing the Team of Localsint and there socials and what not, https://localsint.xyz/

❤3

8 Jul 2026, 16:00 UTC170 views2 reactionsread 9 August 2026

Localsint Team — We've added name search coverage for Canada, the US, and several more countries, added social lookups for Instagram and Telegram, introduced a full name search module with database access and credential data, patched the credits bug, and shipped a handful of visual updates. We're looking for partnerships that could exchange api access with us, if interested contact: @localsintsupport

❤2

7 Jul 2026, 14:29 UTC149 views4 reactionsread 9 August 2026

LocalSint API So we've been running LocalSint as an OSINT dashboard for a while now. Here's the next step: we're handing you the engine itself. Same system that powers our Discord monitoring, breach lookups, and all the cross-platform checks, except now it's a raw API you can wire straight into whatever you're building. No frontend, no filler, just the data. Real talk, most OSINT APIs out there are just Shodan or H…

❤4

6 Jul 2026, 17:21 UTC141 views3 reactionsread 9 August 2026

dm @amidated for 10 free credits so u can try our tool out

❤3

6 Jul 2026, 09:34 UTC155 viewsread 9 August 2026

dm @localsintsupport if you have any servers that you want us to scrape for the discord monitor feature.

6 Jul 2026, 08:43 UTC157 views4 reactionsread 9 August 2026

We've added OathNet, OSINTCat, and SeeKnow as the latest modules in our toolkit. These tools are ready to use now. Coming soon: NOSINT, OSINTKit, and IntelX — please note that NOSINT, OSINTKit, and IntelX are currently down for maintenance while we work on improvements. Stay tuned for updates. — From Localsint For potential bugs use our bot @localsintsupport

❤4

6 Jul 2026, 00:11 UTC161 views4 reactionsread 9 August 2026

If you need any help or run into issues while using LocalSint, our support team is here to assist you. For questions, troubleshooting, or general assistance, please reach out to @localsintsupport and we'll get back to you as soon as possible.

❤4

5 Jul 2026, 23:43 UTC≈1,090 views9 reactionsread 9 August 2026
Photo

Welcome to LocalSint LocalSint is an OSINT tool that actually does what it says. Give it a name, email, phone, or handle and it pulls together what's out there — the open web, breaches, and public records — and checks it before handing it to you. Most tools just wrap the same free APIs and call it a day. We didn't. On top of the sources worth using, we built our own modules you won't find anywhere else. Modules: …

❤9

Showing the 12 most recent of 12 posts we hold for @localsint. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.

“Localsint” (@localsint), 85 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/localsint.

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.