TRUCKING COMPANY ☑️ Position: #ADMINSALES ☑️ Region: Tashkent, Uzbekistan 🇺🇿 ☑️ Experience: No experience required (Strong communication skills are essential) ☑️ Working Hours: 11:00 PM – 7:00 AM ☑️ Salary: To be discussed during the interview. ☑️ Our main requirements: • Excellent communication and interpersonal skills. • Strong sales and customer service mindset. • Responsible, disciplined, and well-organized. …

Channel
HUNTME | GLOBAL
@huntmeglobal
On this record: Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
4,385subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002906889695 |
|---|---|
| Type | Channel |
| Username | @huntmeglobal |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/huntmeglobal |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 17:14 | 4,385 | -3 |
| 11 Aug 2026, 02:31 | 4,388 | -2 |
| 7 Aug 2026, 18:12 | 4,390 | +1 |
| 7 Aug 2026, 13:03 | 4,389 | first reading |
Engagement
22 posts held, back to 29 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 5 pagesof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 64.2%
- avg views ÷ 4,385 subscribers
- Avg views / post
- 2,820
- 22 posts measured
- Reaction rate
- 0.039%
- reactions ÷ views · ER floor
- Posts in window
- 22
- of 22 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. It is computed over the 11 of 22 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 22 (29 July 2026 – 8 August 2026) |
| Views total | 61,958 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 18:17 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.
Reaction mix
11 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 72.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 8 | 72.7% | |
| 🤷♂ | 2 | 18.2% | |
| 🤩 | 1 | 9.09% |
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 11 of the 22 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 11reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 29 July 2026 to 8 August 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
TRUCKING COMPANY ☑️ Position: #ADMINSALES ☑️ Region: Tashkent, Uzbekistan 🇺🇿 ☑️ Experience: No experience required (Strong communication skills are essential) ☑️ Working Hours: 11:00 PM – 7:00 AM ☑️ Salary: To be discussed during the interview. ☑️ Our main requirements: • Excellent communication and interpersonal skills. • Strong sales and customer service mindset. • Responsible, disciplined, and well-organized. …
❤2
NEXORA OPERATIONS COMPANY ☑️ Position: #SALES_MANAGER ONLY FEMALE ☑️ Location: 📍 Tashkent, Shota Rustaveli Street 150 (Near South Railway Station / Janubiy Vokzal) ☑️ Salary: To be discussed during the interview ☑️ Working Hours: • 4:00 PM – 12:00 AM • 5/2 ☑️ Work Format: • Office-based only (No remote work) ☑️ Requirements: • ONLY FEMALE candidates are welcome; • Experience is preferred, but candidates without exp…
❤1
RIVOJ EDUCATION ☑️ Lavozim: #ADMINISTRATOR FAQAT QIZLAR!!! ☑️Hudud: 🇺🇿 Toshkent shahri ☑️Maosh: 3 000 000 – 8 000 000 so'm ☑️ Ish vaqti: • 10:00 – 19:00 ☑️ Asosiy talablarimiz: • 18 yoshdan katta bo‘lishi; • O‘zbek tilida ravon va chiroyli nutqqa ega bo‘lishi; • Sotuv (savdo) sohasida kamida 6 oylik tajriba; • Mas'uliyatli, xushmuomala va jamoada ishlay olishi; • Microsoft Office dasturlaridan foydalana olishi. ☑️…
LLC GOLDEN MINDS ☑️ Position: #SALESMANAGER ☑️ Region: 📍 Tashkent, Uzbekistan 🇺🇿 ☑️ Salary: 6,000,000 – 12,000,000 UZS/month ☑️ Working Schedule: • Full-time • 5/2 ☑️Requirements: • Minimum 1 year of sales experience; • Knowledge of Sales and Marketing; • Strong communication and negotiation skills; • Result-oriented and responsible; • Ability to work in a team. ☑️What We Offer: • Competitive salary; • Career grow…
🤩1
LUCID LOGISTICS ACADEMY ☑️ Position: #DISPATCHER_MENTOR ☑️ Location: 📍 Tashkent, Mirzo Ulugbek District (Darxon) ☑️ Salary: To be discussed during the interview ☑️ Working Hours: • 5:00 PM – 9:00 PM ☑️ Requirements: • Minimum 4+ years of experience in the logistics industry; • Real hands-on experience working with entry-level employees; • Strong knowledge of Amazon Relay and Street Loads; • Excellent mentoring a…
NEXORA OPERATIONS COMPANY ☑️ Position: #SALES_MANAGER ONLY FEMALE ☑️ Location: 📍 Tashkent, Shota Rustaveli Street 150 (Near South Railway Station / Janubiy Vokzal) ☑️ Salary: To be discussed during the interview ☑️ Working Hours: • 4:00 PM – 12:00 AM • 5/2 ☑️ Work Format: • Office-based only (No remote work) ☑️ Requirements: • ONLY FEMALE candidates are welcome; • Experience is preferred, but candidates without exp…
IT COMPANY ☑️ Position: Sales & Customer Support Specialist ☑️ Location: 📍 Tashkent, Yakkasaroy District (Yakkasaroy Wedding Hall) ☑️ Salary: Fixed salary + Commission 💲 ☑️ Work Type: Office-based (No remote) ☑️ Working Hours: 18:00 – 04:00 (Uzbekistan Time) ☑️ Age: 20+ ☑️ Main Requirements: • Male and female candidates are welcome; • Good Russian and fluent English are required; • Confident computer user; • Stro…
❤2
☑️Lavozim: #TARGETOLOGIST ☑️ Hudud: 🇺🇿 Toshkent shahri, Olmazor tumani, Kichik Halqa Yo‘li 12A ☑️ Kompaniya: Car2Sell ☑️ Maosh: 800$ ☑️ Ish turi: Ofisdan ishlash ☑️ Ish vaqti: 18:00 – 03:00 • (AQSh bozori bo‘yicha) ☑️ Asosiy talablarimiz: • Ingliz tilini yaxshi darajada bilishi ; • 1–3 yillik Targetolog sifatida ish tajribasi; • Facebook, Instagram va Google Ads platformalarida reklama kampaniyalarini yaratish va bo…
TRUCKING COMPANY ☑️ Position: #JUNIORANALYST ☑️ Region: 📍Tashkent, Uzbekistan🇺🇿 ☑️ Experience: required ☑️ Shift: 13:00 - 22:00 ☑️ Requirements: Ability to analyze information, news, and company reports. ☑️ Analyzing charts and market trends. ☑️ English proficiency: minimum B2 level ☑️ Strong analytical skills. ☑️ Ability to work with data and structure information. ☑️ Salary: Discussed on the interview💲 GET A JOB …
TRUCKING COMPANY ☑️ Position: #BRANDFACE 📍 Region: Tashkent, Uzbekistan 🇺🇿 🕒 Work Schedule: Flexible 💰 Salary: To be discussed during the interview. 💼 Experience: Minimum 1 year of experience as a Brand Face, with participation in multiple commercial projects. Key Responsibilities: ☑️ Strong on-camera presence and confidence. ☑️ Participate in marketing campaigns and content creation. ☑️ Maintain a professional and…
SHAMCRM COMPANY ☑️ Position: #B2BSALESMANAGER ☑️Region: Tashkent, Uzbekistan 🇺🇿 ☑️Location: Mirzo Ulug'bek District, Pushkin Metro, Oasis Business Center ☑️Working Hours: Monday – Friday | 9:00 AM – 6:00 PM ☑️Salary: 4,000,000 – 12,000,000 UZS (Salary + KPI) ☑️Experience: Minimum 6 months in Sales (B2B sales experience is an advantage) ☑️ Our main requirements: ☑️ At least 6 months of experience in the sales field.…
❤1
Showing the 12 most recent of 22 posts we hold for @huntmeglobal. 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.
Posts edited after publishing
@huntmeglobal edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 8 August 2026
- Most recent edit
- 8 August 2026
Citation-graph rank
Citation-graph rank — 187,557 of 1,481,502entries 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.
Mentions
Named by 2 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“HUNTME | GLOBAL” (@huntmeglobal), 4,385 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/huntmeglobal.
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.