BIZTRAC BETA
Geological surveying

ARKTISK GEOTEK AS

Org. no. 921129092 Limited company (AS) Kvænangen Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 6.4m
Operating profit NOK 536,000
Equity NOK 2.9m
Incorporated 2018
Employees 11
Share capital NOK 30,000

ARKTISK GEOTEK AS is registered as a limited company in Kvænangen, Troms with organisation number 921129092. The business is classified under geological surveying (NACE 71.122). The company was incorporated in 2018 and has 11 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Levere geologisk rådgivning i forbindelse med kartlegging av grunnforhold og vurdering av naturfarer. Selskapet tilbyr også prosjektledelse og feltbefaring innen naturforvaltning”. The most recent filed accounts, for the 2025 financial year, show NOK 6.4m in revenue and NOK 536,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.4m
Operating profit
NOK 536,000
Equity
NOK 2.9m
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
2.71
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
65.6%
Very good
Equity as a share of total capital

Who owns ARKTISK GEOTEK AS?

HERMANN OLAUSSEN HERMANSEN
ARKTISK GEOTEK AS
NOK 6.4m rev. · NOK 536,000 profit

ARKTISK GEOTEK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARKTISK GEOTEK AS

Who owns ARKTISK GEOTEK AS?

HERMANN OLAUSSEN HERMANSEN is the largest registered owner, with 50.0%.

What is the revenue of ARKTISK GEOTEK AS?

ARKTISK GEOTEK AS had revenue of NOK 6.4m in 2025.

Who is the general manager of ARKTISK GEOTEK AS?

Hermann Olaussen Hermansen is registered as general manager of ARKTISK GEOTEK AS.

Where is ARKTISK GEOTEK AS based?

ARKTISK GEOTEK AS has its business address in Sørstraumen.

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

Report a problem

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