BIZTRAC BETA
Rental and operating of own or leased real estate

SKAGERAK BOLIG AS

Org. no. 913332547 Limited company (AS) Sandefjord Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.2m
Equity NOK 563,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SKAGERAK BOLIG AS is registered as a limited company in Sandefjord, Vestfold with organisation number 913332547. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og utleie av eiendom og andre eiendeler som naturlig faller sammen med dette, herunder å delta i andre selskaper, samt kjøp og salg av aksjer og eierandeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.2m
Equity
NOK 563,000
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.1%
Weak
Equity as a share of total capital

Who owns SKAGERAK BOLIG AS?

SKAGERAK INVEST AS
SKAGERAK BOLIG AS
NOK 1.8m rev. · NOK 1.2m profit

SKAGERAK BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKAGERAK BOLIG AS

Who owns SKAGERAK BOLIG AS?

SKAGERAK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SKAGERAK BOLIG AS?

SKAGERAK BOLIG AS had revenue of NOK 1.8m in 2024.

Where is SKAGERAK BOLIG AS based?

SKAGERAK BOLIG AS has its business address in Sandefjord.

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.