biztrac. BETA
COMPANY REGISTER PROFILE
912678342 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

ARCTIC BOLIG AS

Org. no. 912678342 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 19.0m
Operating profit NOK 1.1m
Equity NOK 2.2m
Incorporated 2013
Employees 9
Share capital NOK 30,000

ARCTIC BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 912678342. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2013 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Oppføring av bolig/nybygg, mur-/pussearbeid, rådgivning og entreprenørvirksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 19.0m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 19.0m
▲ +170 %
Operating profit
NOK 1.1m
▲ +1077 %
Equity
NOK 2.2m
▲ +46 %
Est. value
NOK 3.7m

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
15.7%
Very good
Return on total assets
Solidity
25.2%
Good
Equity as a share of total capital

Who owns ARCTIC BOLIG AS?

ARCTIC BOLIG AS
NOK 19.0m rev. · NOK 1.1m profit

ARCTIC BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARCTIC BOLIG AS

Who owns ARCTIC BOLIG AS?

K. REX HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ARCTIC BOLIG AS?

ARCTIC BOLIG AS had revenue of NOK 19.0m in 2025.

Who is the general manager of ARCTIC BOLIG AS?

Kjeld Andersen is registered as general manager of ARCTIC BOLIG AS.

Where is ARCTIC BOLIG AS based?

ARCTIC BOLIG AS has its business address in Oslo.

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.