BIZTRAC BETA
Rental and operating of own or leased real estate

OXEN EIENDOM AS

Org. no. 929766784 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 363,000
Operating profit NOK 159,000
Equity NOK −150,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−150k kr).
  • Nylig endring 2026-08-04 Adresseendring registrert 2026-08-04.

OXEN EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 929766784. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøpe, selge, eie, leie ut, utvikle og drifte fast eiendom, samt eie aksjer og andeler i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 363,000 in revenue and NOK 159,000 in operating profit.

Key figures · 2025

Revenue
NOK 363,000
Operating profit
NOK 159,000
Equity
NOK −150,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
-0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.8%
Weak
Equity as a share of total capital

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

Who owns OXEN EIENDOM AS?

ASTR HOLDING AS
OXEN EIENDOM AS
NOK 363,000 rev. · NOK 159,000 profit

OXEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OXEN EIENDOM AS

Who owns OXEN EIENDOM AS?

ASTR HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OXEN EIENDOM AS?

OXEN EIENDOM AS had revenue of NOK 363,000 in 2025.

Where is OXEN EIENDOM AS based?

OXEN EIENDOM AS has its business address in Fornebu.

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.