BIZTRAC BETA
General primary education

OASEN EIENDOM G15 AS

Org. no. 895848832 Limited company (AS) Kristiansand Incorporated 2010 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 856,000
Equity NOK 442,000
Incorporated 2010
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

OASEN EIENDOM G15 AS is registered as a limited company in Kristiansand, Agder with organisation number 895848832. The business is classified under general primary education (NACE 85.201). The company was incorporated in 2010. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte fast eiendom samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 856,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 856,000
Equity
NOK 442,000
Est. value
NOK 3.2m

Financial health · 2024

Liquidity
0.61
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.9%
Weak
Equity as a share of total capital

Who owns OASEN EIENDOM G15 AS?

OASEN HOLDING SØGNE AS
OASEN EIENDOM G15 AS
NOK 1.0m rev. · NOK 856,000 profit

OASEN EIENDOM G15 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OASEN EIENDOM G15 AS

Who owns OASEN EIENDOM G15 AS?

OASEN HOLDING SØGNE AS is the largest registered owner, with 100.0%.

What is the revenue of OASEN EIENDOM G15 AS?

OASEN EIENDOM G15 AS had revenue of NOK 1.0m in 2025.

Who is the general manager of OASEN EIENDOM G15 AS?

Øyvind Haugland is registered as general manager of OASEN EIENDOM G15 AS.

Where is OASEN EIENDOM G15 AS based?

OASEN EIENDOM G15 AS has its business address in Søgne.

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.