BIZTRAC BETA
Construction of residential and non-residential buildings

ARKTISK BYGG AS

Org. no. 918772642 Limited company (AS) Vadsø Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 26.1m
Operating profit NOK 943,000
Equity NOK 7.0m
Incorporated 2017
Employees 17
Share capital NOK 60,000

ARKTISK BYGG AS is registered as a limited company in Vadsø, Finnmark with organisation number 918772642. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017 and has 17 registered employees. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Salg av snekker/byggetjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 26.1m in revenue and NOK 943,000 in operating profit.

Key figures · 2024

Revenue
NOK 26.1m
Operating profit
NOK 943,000
Equity
NOK 7.0m
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns ARKTISK BYGG AS?

ERLANDS1 HOLDING AS
ARKTISK BYGG AS
NOK 26.1m rev. · NOK 943,000 profit

ARKTISK BYGG AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ARKTISK BYGG AS own?

ARKTISK BYGG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARKTISK BYGG AS

Who owns ARKTISK BYGG AS?

ERLANDS1 HOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of ARKTISK BYGG AS?

ARKTISK BYGG AS had revenue of NOK 26.1m in 2024.

Who is the general manager of ARKTISK BYGG AS?

Erland Helge Erlandsen is registered as general manager of ARKTISK BYGG AS.

Where is ARKTISK BYGG AS based?

ARKTISK BYGG AS has its business address in Vadsø.

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.