BIZTRAC BETA
Buying and selling of own real estate

SYDENHELSE & BOLIG AS

Org. no. 981487214 Limited company (AS) Holmestrand Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 48,000
Operating profit NOK −32,000
Equity NOK 435,000
Incorporated 2000
Share capital NOK 400,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−32k kr).

SYDENHELSE & BOLIG AS is registered as a limited company in Holmestrand, Vestfold with organisation number 981487214. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2000. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Eiendom investering salgsformidling.”. The most recent filed accounts, for the 2025 financial year, show NOK 48,000 in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 48,000
Operating profit
NOK −32,000
Equity
NOK 435,000
Est. value
NOK 356,000

Financial health · 2024

Liquidity
0.26
Not satisfactory
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 SYDENHELSE & BOLIG AS?

MARIA ALITA BIRKELAND
SYDENHELSE & BOLIG AS
NOK 48,000 rev. · NOK −32,000 profit

SYDENHELSE & BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYDENHELSE & BOLIG AS

Who owns SYDENHELSE & BOLIG AS?

MARIA ALITA BIRKELAND is the largest registered owner, with 100.0%.

What is the revenue of SYDENHELSE & BOLIG AS?

SYDENHELSE & BOLIG AS had revenue of NOK 48,000 in 2025.

Who is the general manager of SYDENHELSE & BOLIG AS?

Gunnar Birkeland is registered as general manager of SYDENHELSE & BOLIG AS.

Where is SYDENHELSE & BOLIG AS based?

SYDENHELSE & BOLIG AS has its business address in Sande I Vestfold.

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.