BIZTRAC BETA
COMPANY REGISTER PROFILE
817500382 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other real estate activities on a fee or contract basis

ØVREBERGBYGGET AS

Org. no. 817500382 Limited company (AS) Stryn Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 1.5m
Equity NOK 33.9m
Incorporated 1987
Share capital NOK 100,000

ØVREBERGBYGGET AS is registered as a limited company in Stryn, Vestland with organisation number 817500382. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Eiendomsforvaltning, samt hva hermed står i forbindelse, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
▲ +2 %
Operating profit
NOK 1.5m
▼ −11 %
Equity
NOK 33.9m
▲ +8 %
Est. value
NOK 27.4m

Financial health · 2025

Liquidity
16.22
Very good
Current assets ÷ current liabilities
Profitability
10.3%
Good
Return on total assets
Solidity
95.3%
Very good
Equity as a share of total capital

Who owns ØVREBERGBYGGET AS?

ØVREBERGBYGGET AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ØVREBERGBYGGET AS own?

ØVREBERGBYGGET AS holds stakes in 6 companies:

See the full ownership structure →

Group structure

ØVREBERGBYGGET AS er morselskap for 1 datterselskap:

Frequently asked questions about ØVREBERGBYGGET AS

Who owns ØVREBERGBYGGET AS?

ARMA AS is the largest registered owner, with 28.0%.

What is the revenue of ØVREBERGBYGGET AS?

ØVREBERGBYGGET AS had revenue of NOK 2.4m in 2025.

Where is ØVREBERGBYGGET AS based?

ØVREBERGBYGGET AS has its business address in Stryn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.