biztrac. BETA
COMPANY REGISTER PROFILE
936610161 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Holiday and other short-stay accommodation

PUREARCTIC AS

Org. no. 936610161 Limited company (AS) Målselv Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 88,000
Operating profit NOK 9,000
Equity NOK 37,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-18.

PUREARCTIC AS is registered as a limited company in Målselv, Troms with organisation number 936610161. The business is classified under holiday and other short-stay accommodation (NACE 55.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drifte og forvalte eiendom eiet i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 88,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 88,000
Operating profit
NOK 9,000
Equity
NOK 37,000
Est. value
NOK 44,000

Financial health · 2025

Liquidity
-0.95
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
10.0%
Weak
Equity as a share of total capital

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

Who owns PUREARCTIC AS?

PUREARCTIC AS
NOK 88,000 rev. · NOK 9,000 profit

PUREARCTIC AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PUREARCTIC AS own?

PUREARCTIC AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PUREARCTIC AS

Who owns PUREARCTIC AS?

Knut Håvard Overvik is the largest registered owner, with 100.0%.

What is the revenue of PUREARCTIC AS?

PUREARCTIC AS had revenue of NOK 88,000 in 2025.

Where is PUREARCTIC AS based?

PUREARCTIC AS has its business address in Bardufoss.

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.