BIZTRAC BETA
Rental and operating of own or leased real estate

BORGESKOGEN ØST TOMT 18 AS

Org. no. 929915038 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 255,000
Operating profit NOK 68,000
Equity NOK 3.1m
Incorporated 2022
Share capital NOK 60,000

Signals

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

BORGESKOGEN ØST TOMT 18 AS is registered as a limited company in Asker, Akershus with organisation number 929915038. 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 60,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og drift av eiendom samt å eie aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 255,000 in revenue and NOK 68,000 in operating profit.

Key figures · 2024

Revenue
NOK 255,000
Operating profit
NOK 68,000
Equity
NOK 3.1m
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
5.15
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.5%
Good
Equity as a share of total capital

Who owns BORGESKOGEN ØST TOMT 18 AS?

OXFOR EIENDOM AS
BORGESKOGEN ØST TOMT 18 AS
NOK 255,000 rev. · NOK 68,000 profit

BORGESKOGEN ØST TOMT 18 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORGESKOGEN ØST TOMT 18 AS

Who owns BORGESKOGEN ØST TOMT 18 AS?

OXFOR EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of BORGESKOGEN ØST TOMT 18 AS?

BORGESKOGEN ØST TOMT 18 AS had revenue of NOK 255,000 in 2024.

Where is BORGESKOGEN ØST TOMT 18 AS based?

BORGESKOGEN ØST TOMT 18 AS has its business address in Asker.

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.