BIZTRAC BETA
Construction of residential and non-residential buildings

OSLOFJORDEN BYGG AS

Org. no. 976465415 Limited company (AS) Råde Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 10.8m
Operating profit NOK 272,000
Equity NOK 1.0m
Incorporated 1996
Employees 7
Share capital NOK 100,000

OSLOFJORDEN BYGG AS is registered as a limited company in Råde, Østfold with organisation number 976465415. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1996 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Bygg- og tømrervirksomhet og å engasjere seg i beslektede virksomheter samt alt hva som herved måtte stå i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.8m in revenue and NOK 272,000 in operating profit.

Key figures · 2025

Revenue
NOK 10.8m
Operating profit
NOK 272,000
Equity
NOK 1.0m
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.8%
Good
Equity as a share of total capital

Who owns OSLOFJORDEN BYGG AS?

JOHN WILLAS RØSTAD
OSLOFJORDEN BYGG AS
NOK 10.8m rev. · NOK 272,000 profit

OSLOFJORDEN BYGG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSLOFJORDEN BYGG AS

Who owns OSLOFJORDEN BYGG AS?

JOHN WILLAS RØSTAD is the largest registered owner, with 50.0%.

What is the revenue of OSLOFJORDEN BYGG AS?

OSLOFJORDEN BYGG AS had revenue of NOK 10.8m in 2025.

Who is the general manager of OSLOFJORDEN BYGG AS?

Ole Martin Sukke is registered as general manager of OSLOFJORDEN BYGG AS.

Where is OSLOFJORDEN BYGG AS based?

OSLOFJORDEN BYGG AS has its business address in Råde.

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.