BIZTRAC BETA
Rental and operating of own or leased real estate

BILLINGSTADSLETTA 14-18 AS

Org. no. 934959388 Limited company (AS) Asker Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 48.4m
Operating profit NOK 37.8m
Equity NOK 92.2m
Incorporated 1983
Share capital NOK 5.0m

Signals

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

BILLINGSTADSLETTA 14-18 AS is registered as a limited company in Asker, Akershus with organisation number 934959388. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1983. Registered share capital is NOK 5.0m. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 48.4m in revenue and NOK 37.8m in operating profit.

Key figures · 2024

Revenue
NOK 48.4m
Operating profit
NOK 37.8m
Equity
NOK 92.2m
Est. value
NOK 137.3m

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
44.3%
Very good
Equity as a share of total capital

Who owns BILLINGSTADSLETTA 14-18 AS?

BILLINGSTADSLETTA AS
BILLINGSTADSLETTA 14-18 AS
NOK 48.4m rev. · NOK 37.8m profit

BILLINGSTADSLETTA 14-18 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILLINGSTADSLETTA 14-18 AS

Who owns BILLINGSTADSLETTA 14-18 AS?

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

What is the revenue of BILLINGSTADSLETTA 14-18 AS?

BILLINGSTADSLETTA 14-18 AS had revenue of NOK 48.4m in 2024.

Where is BILLINGSTADSLETTA 14-18 AS based?

BILLINGSTADSLETTA 14-18 AS has its business address in Billingstad.

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.