BIZTRAC BETA
Rental and operating of own or leased real estate

BALKEBY EIENDOM AS

Org. no. 912812669 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 15.1m
Operating profit NOK 10.1m
Equity NOK 7.1m
Incorporated 2013
Share capital NOK 268,000

Signals

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

BALKEBY EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 912812669. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 268,000, divided into 1000 shares. The company's stated purpose is: “Være et investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom, og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.1m in revenue and NOK 10.1m in operating profit.

Key figures · 2024

Revenue
NOK 15.1m
Operating profit
NOK 10.1m
Equity
NOK 7.1m
Est. value
NOK 21.6m

Financial health · 2024

Liquidity
1.87
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.8%
Satisfactory
Equity as a share of total capital

Who owns BALKEBY EIENDOM AS?

ALPHA XL AS
BALKEBY EIENDOM AS
NOK 15.1m rev. · NOK 10.1m profit

BALKEBY EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BALKEBY EIENDOM AS

Who owns BALKEBY EIENDOM AS?

ALPHA XL AS is the largest registered owner, with 100.0%.

What is the revenue of BALKEBY EIENDOM AS?

BALKEBY EIENDOM AS had revenue of NOK 15.1m in 2024.

Where is BALKEBY EIENDOM AS based?

BALKEBY EIENDOM AS has its business address in Oslo.

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.