BIZTRAC BETA
Rental and operating of own or leased real estate

OSEN 8 AS

Org. no. 991126759 Limited company (AS) Stord Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK −4.1m
Equity NOK −3.6m
Incorporated 2007
Share capital NOK 30.2m

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−3,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,1 mill kr).
  • Nylig endring 2026-06-10 Aksjekapital registrert 2026-06-10.

OSEN 8 AS is registered as a limited company in Stord, Vestland with organisation number 991126759. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 30.2m, divided into 302000 shares. The company's stated purpose is: “Forvalte fast eiendom, herunder drift, kjøp, salg og oppføring av fast eiendom, samt å delta i foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK −4.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK −4.1m
Equity
NOK −3.6m

Financial health · 2025

Liquidity
5.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-11.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns OSEN 8 AS?

RUNESTAD INVESTERING AS
OSEN 8 AS
NOK 3.3m rev. · NOK −4.1m profit

OSEN 8 AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSEN 8 AS

Who owns OSEN 8 AS?

RUNESTAD INVESTERING AS is the largest registered owner, with 50.0%.

What is the revenue of OSEN 8 AS?

OSEN 8 AS had revenue of NOK 3.3m in 2024.

Where is OSEN 8 AS based?

OSEN 8 AS has its business address in Stord.

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.