biztrac. BETA
COMPANY REGISTER PROFILE
935851351 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of tour guides

KIRKENES TOURS AS

Org. no. 935851351 Limited company (AS) Sør-Varanger Incorporated 2025 Active
Revenue 2025 NOK 202,000
Operating profit NOK −29,000
Equity NOK −4,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4k kr).

KIRKENES TOURS AS is registered as a limited company in Sør-Varanger, Finnmark with organisation number 935851351. The business is classified under activities of tour guides (NACE 79.902). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3 shares. The company's stated purpose is: “Salg og drift av reiselivstjenester, inkludert turer, aktiviteter og transport i Kirkenes og omegn, samt annen virksomhet som naturlig henger sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 202,000 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 202,000
Operating profit
NOK −29,000
Equity
NOK −4,000

Financial health · 2025

Liquidity
13.34
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-0.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KIRKENES TOURS AS?

KIRKENES TOURS AS
NOK 202,000 rev. · NOK −29,000 profit

KIRKENES TOURS AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KIRKENES TOURS AS

Who owns KIRKENES TOURS AS?

Henrik Hoffmann is the largest registered owner, with 33.3%.

What is the revenue of KIRKENES TOURS AS?

KIRKENES TOURS AS had revenue of NOK 202,000 in 2025.

Where is KIRKENES TOURS AS based?

KIRKENES TOURS AS has its business address in Jarfjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.