biztrac. BETA
COMPANY REGISTER PROFILE
914533287 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

BILLINGSTADSLETTA 11 AS

Org. no. 914533287 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 18.2m
Operating profit NOK 12.5m
Equity NOK 53.3m
Incorporated 2014
Share capital NOK 1.0m

BILLINGSTADSLETTA 11 AS is registered as a limited company in Oslo, Oslo with organisation number 914533287. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i eiendom, aksjer og andre eierandeler, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.2m in revenue and NOK 12.5m in operating profit.

Former names: INCEPTUM 823 AS, BILLINGSTADSLETTA 11 HOLDING AS

Key figures · 2025

Revenue
NOK 18.2m
▲ +1 %
Operating profit
NOK 12.5m
▼ −0 %
Equity
NOK 53.3m
▼ −1 %
Est. value
NOK 48.1m

Financial health · 2025

Liquidity
0.09
Not satisfactory
Current assets ÷ current liabilities
Profitability
6.9%
Satisfactory
Return on total assets
Solidity
19.7%
Good
Equity as a share of total capital

Who owns BILLINGSTADSLETTA 11 AS?

BILLINGSTADSLETTA 11 AS
NOK 18.2m rev. · NOK 12.5m profit

BILLINGSTADSLETTA 11 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILLINGSTADSLETTA 11 AS

Who owns BILLINGSTADSLETTA 11 AS?

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

What is the revenue of BILLINGSTADSLETTA 11 AS?

BILLINGSTADSLETTA 11 AS had revenue of NOK 18.2m in 2025.

Where is BILLINGSTADSLETTA 11 AS based?

BILLINGSTADSLETTA 11 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.