BIZTRAC BETA
Rental and operating of own or leased real estate

OASEN EIENDOM AS

Org. no. 977175232 Limited company (AS) Haugesund Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 561,000
Operating profit NOK 331,000
Equity NOK 1.5m
Incorporated 1996
Share capital NOK 1.2m

Signals

1 flags
  • Nylig endring 2026-03-03 Adresseendring registrert 2026-03-03.

OASEN EIENDOM AS is registered as a limited company in Haugesund, Rogaland with organisation number 977175232. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 1.2m, divided into 50000 shares. The company's stated purpose is: “Handel i verdipapirer, kjøp, salg og utleie av fast eiendom samt delta i andre foretak med tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 561,000 in revenue and NOK 331,000 in operating profit.

Key figures · 2024

Revenue
NOK 561,000
Operating profit
NOK 331,000
Equity
NOK 1.5m
Est. value
NOK 1.7m

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.0%
Satisfactory
Equity as a share of total capital

Who owns OASEN EIENDOM AS?

BIRGER NETLAND
OASEN EIENDOM AS
NOK 561,000 rev. · NOK 331,000 profit

OASEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OASEN EIENDOM AS

Who owns OASEN EIENDOM AS?

BIRGER NETLAND is the largest registered owner, with 70.0%.

What is the revenue of OASEN EIENDOM AS?

OASEN EIENDOM AS had revenue of NOK 561,000 in 2024.

Who is the general manager of OASEN EIENDOM AS?

Bjarne Netland is registered as general manager of OASEN EIENDOM AS.

Where is OASEN EIENDOM AS based?

OASEN EIENDOM AS has its business address in Haugesund.

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.