IP Location Lookup Tool

flag Moscow, Moscow City, Russia
Threat 0
AS8359 (MTS PJSC)
MTS PJSC

IP address

81.195.187.37

Geolocation Info

IP

81.195.187.37

City

Moscow

District / County

Tverskoy

State Code

RU-MOW

State / Province

Moscow City

Country Name

Russia

Country Name Official

Russian Federation

Country Capital

Moscow

Country Code (ISO-2)

RU

Country Code (ISO-3)

RUS

Country Flag

Flag link

Coordinates

55.75583, 37.61730

Continent Name

Europe

Continent Code

EU

Geoname ID

10231526

ZipCode

109012

Is EU?

false

Country Emoji

🇷🇺

IP Geolocation API (IPv4/IPv6 + Domain Lookup)

Convert 81.195.187.37 into precise GeoIP signals - country/region/city, latitude/longitude, postal code, and enriched metadata - to power localization, analytics, and compliance-aware routing.

Powered by IPGeolocation's IP Location API (single + bulk lookups) with optional enrichment modules via include (e.g., geo_accuracy, user_agent, security, abuse, hostname).

Get IP Location API Key IP Location API Docs

ASN Info

AS Number

AS8359

Organization

MTS PJSC

Country

RU

ASN Lookup API (Peering + WHOIS Signals)

Map 81.195.187.37 to its announcing ASN AS8359 and retrieve organization context. Expand into peers, upstreams, downstreams, routes, and WHOIS response data for peering analysis, block decisions, and attribution.

Use the dedicated ASN API for deep network-relationship data (or use /v3/ipgeo for basic ASN fields).

Get ASN API Key ASN API Docs

Regional Overview

Calling Code

+7

Languages

ru, tt, xal, cau, ady, kv, ce, tyv, cv, udm, tut, mns, bua, myv, mdf, chm, ba, inh, tut, kbd, krc, av, sah, nog

Country TLD

.ru

Regional Metadata (Country, State/Region, Languages)

Regional traits derived from 81.195.187.37 help adapt language, policy, and user experience for Russia traffic - including country/region/city signals plus country metadata like calling code, TLD, and languages.

Regional + country metadata are included in the default /v3/ipgeo response. Add optional modules (e.g., geo_accuracy or dma) via include when you need finer targeting.

Get IP Location API Key Region & Country Metadata Docs

Currency Info

Currency Code

RUB

Currency Name

Russian Ruble

Currency Symbol

₽

Exchange Rate

RUB

Currency Mapping (ISO 4217 Code, Name, Symbol)

Auto-map 81.195.187.37 to currency context (ISO 4217 code, currency name, and symbol) to localize checkout defaults, pricing display, and payment validation rules.

Currency is included by default in the /v3/ipgeo response - ideal for localization and FX-aware pricing workflows.

Get IP Location API Key Currency Fields Docs

TimeZone Info

Name

Europe/Moscow

Offset

3.0

Offset With DST

3.0

Current Time

2026-03-05 17:44:53.317+0300

Current Time Unix

1.772721893317E9

Current TZ Abbreviation

MSK

Current TZ Full Name

Moscow Standard Time

Standard TZ Abbreviation

MSK

Standard TZ Full Name

Moscow Standard Time

DST TZ Abbreviation

N/A

DST TZ Full Name

N/A

Is DST

false

DST Savings

0

DST Exists

false

Timezone Intelligence (Offsets, DST, Local Time)

Align alerts, receipts, and user-facing timestamps with local expectations by mapping 81.195.187.37 to timezone name, UTC offsets, DST rules, and current local time.

Timezone data appears inside /v3/ipgeo and is also available via the dedicated Timezone API (/v3/timezone), which supports lookups by IP, coordinates, address, timezone name, and airport codes.

Get Timezone API Key Timezone API Docs
Response Preview 
{
  "ip" : "81.195.187.37",
  "hostname" : "81.195.187.37",
  "location" : {
    "district" : "Tverskoy",
    "city" : "Moscow",
    "locality" : "Moscow",
    "zipcode" : "109012",
    "latitude" : "55.75583",
    "longitude" : "37.61730",
    "continent_code" : "EU",
    "continent_name" : "Europe",
    "country_code2" : "RU",
    "country_code3" : "RUS",
    "country_name" : "Russia",
    "country_name_official" : "Russian Federation",
    "country_capital" : "Moscow",
    "state_prov" : "Moscow City",
    "state_code" : "RU-MOW",
    "accuracy_radius" : "23.04",
    "confidence" : "high",
    "dma_code" : "",
    "is_eu" : false,
    "country_flag" : "https://ipgeolocation.io/static/flags/ru_64.png",
    "geoname_id" : "10231526",
    "country_emoji" : "🇷🇺"
  },
  "country_metadata" : {
    "tld" : ".ru",
    "languages" : [ "ru", "tt", "xal", "cau", "ady", "kv", "ce", "tyv", "cv", "udm", "tut", "mns", "bua", "myv", "mdf", "chm", "ba", "inh", "tut", "kbd", "krc", "av", "sah", "nog" ],
    "calling_code" : "+7"
  },
  "network" : {
    "route" : "81.195.0.0/16",
    "connection_type" : "",
    "is_anycast" : false
  },
  "currency" : {
    "code" : "RUB",
    "name" : "Russian Ruble",
    "symbol" : "₽"
  },
  "asn" : {
    "organization" : "MTS PJSC",
    "country" : "RU",
    "type" : "ISP",
    "domain" : "mtu.ru",
    "rir" : "RIPE",
    "as_number" : "AS8359",
    "date_allocated" : "2002-09-17"
  },
  "company" : {
    "name" : "MTS PJSC",
    "type" : "",
    "domain" : "mts.ru"
  },
  "security" : {
    "threat_score" : 0,
    "is_tor" : false,
    "is_proxy" : false,
    "proxy_provider_names" : [ ],
    "proxy_confidence_score" : 0,
    "proxy_last_seen" : "",
    "is_residential_proxy" : false,
    "is_vpn" : false,
    "vpn_provider_names" : [ ],
    "vpn_confidence_score" : 0,
    "vpn_last_seen" : "",
    "is_relay" : false,
    "relay_provider_name" : "",
    "is_anonymous" : false,
    "is_known_attacker" : false,
    "is_spam" : false,
    "is_bot" : false,
    "is_cloud_provider" : false,
    "cloud_provider_name" : ""
  },
  "abuse" : {
    "route" : "81.195.187.32/28",
    "country" : "RU",
    "name" : "MTU Abuse-c Bender",
    "organization" : "",
    "kind" : "group",
    "address" : "PJSC MTS / former CJSC Comstar-Direct\nSmolenskaya-Sennaya, 27\nP.O. BOX 38 123001\nMoscow, Russia",
    "emails" : [ "abuse@mtu.ru" ],
    "phone_numbers" : [ "+7 495 956-07-07", " +7 495 956-00-00" ]
  },
  "time_zone" : {
    "name" : "Europe/Moscow",
    "offset" : 3.0,
    "offset_with_dst" : 3.0,
    "current_time" : "2026-03-05 17:44:53.317+0300",
    "current_time_unix" : 1.772721893317E9,
    "current_tz_abbreviation" : "MSK",
    "current_tz_full_name" : "Moscow Standard Time",
    "standard_tz_abbreviation" : "MSK",
    "standard_tz_full_name" : "Moscow Standard Time",
    "is_dst" : false,
    "dst_savings" : 0,
    "dst_exists" : false,
    "dst_tz_abbreviation" : "",
    "dst_tz_full_name" : "",
    "dst_start" : { },
    "dst_end" : { }
  },
  "user_agent" : {
    "user_agent_string" : "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)",
    "name" : "ClaudeBot",
    "type" : "Robot",
    "version" : "1.0",
    "version_major" : "1",
    "device" : {
      "name" : "Anthropic ClaudeBot",
      "type" : "Robot",
      "brand" : "Anthropic",
      "cpu" : "Unknown"
    },
    "engine" : {
      "name" : "ClaudeBot",
      "type" : "Robot",
      "version" : "1.0",
      "version_major" : "1"
    },
    "operating_system" : {
      "name" : "Cloud",
      "type" : "Cloud",
      "version" : "??",
      "build" : "??",
      "version_major" : "??"
    }
  }
}

Ready to get started?Get Started with IP Intelligence API Today

Get Started
CTA Illustration

Frequently Asked Questions

These answers are generated from the current data snapshot for 81.195.187.37.

The latest lookup maps 81.195.187.37 to Moscow, Moscow City, Russia. Geolocation is approximate and should be treated as city/region level guidance.
This page currently shows ASN AS8359 and company MTS PJSC. ASN and company attribution can change as routing and ownership records are updated.
The reported connection type for 81.195.187.37 is not published. This value helps with traffic analytics, abuse prevention, and policy routing decisions.
The current timezone record for 81.195.187.37 is Europe/Moscow. Teams commonly use this signal to localize timestamps, notifications, and fraud models.
IP intelligence is dynamic. Routing, ASN ownership, company names, and security posture can change over time, so this page should be treated as a point-in-time lookup for 81.195.187.37.
Use the JSON response on this page for testing, then move to production API workflows with structured fields for geolocation, network, ASN, security, abuse, and timezone data. Read documentation.