biztrac. BETA
COMPANY REGISTER PROFILE
916175353 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

BERGHEIM SYD AS

Org. no. 916175353 Limited company (AS) Fredrikstad Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 12.8m
Operating profit NOK 3.0m
Equity NOK 34.2m
Incorporated 2015
Share capital NOK 180,000

BERGHEIM SYD AS is registered as a limited company in Fredrikstad, Østfold with organisation number 916175353. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2015. Registered share capital is NOK 180,000, divided into 2220000 shares. The company's stated purpose is: “Eiendomsutvikling og kjøp og salg av eiendom samt det som måtte høre til.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.8m in revenue and NOK 3.0m in operating profit.

Former names: MELK PROSJEKTER AS

Key figures · 2025

Revenue
NOK 12.8m
▼ −32 %
Operating profit
NOK 3.0m
▼ −76 %
Equity
NOK 34.2m
▲ +22 %
Est. value
NOK 39.6m

Financial health · 2025

Liquidity
3.56
Very good
Current assets ÷ current liabilities
Profitability
13.4%
Good
Return on total assets
Solidity
50.9%
Very good
Equity as a share of total capital

Who owns BERGHEIM SYD AS?

BERGHEIM SYD AS
NOK 12.8m rev. · NOK 3.0m profit

BERGHEIM SYD AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BERGHEIM SYD AS own?

BERGHEIM SYD AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

BERGHEIM SYD AS er morselskap for 1 datterselskap:

Frequently asked questions about BERGHEIM SYD AS

Who owns BERGHEIM SYD AS?

XPROCO AS is the largest registered owner, with 50.0%.

What is the revenue of BERGHEIM SYD AS?

BERGHEIM SYD AS had revenue of NOK 12.8m in 2025.

Where is BERGHEIM SYD AS based?

BERGHEIM SYD AS has its business address in Manstad.

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.