BIZTRAC BETA
Rental and operating of own or leased real estate

BUSSANLEGG KLOPPAVEIEN 16 AS

Org. no. 985874298 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 3.0m
Equity NOK 9.1m
Incorporated 2003
Share capital NOK 1.0m

Signals

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

BUSSANLEGG KLOPPAVEIEN 16 AS is registered as a limited company in Oslo, Oslo with organisation number 985874298. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 1.0m, divided into 1 shares. 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 2025 financial year, show NOK 4.5m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK 3.0m
Equity
NOK 9.1m
Est. value
NOK 12.3m

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.1%
Good
Equity as a share of total capital

Who owns BUSSANLEGG KLOPPAVEIEN 16 AS?

SPORVEIEN BUSSANLEGG AS
BUSSANLEGG KLOPPAVEIEN 16 AS
NOK 4.5m rev. · NOK 3.0m profit

BUSSANLEGG KLOPPAVEIEN 16 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUSSANLEGG KLOPPAVEIEN 16 AS

Who owns BUSSANLEGG KLOPPAVEIEN 16 AS?

SPORVEIEN BUSSANLEGG AS is the largest registered owner, with 100.0%.

What is the revenue of BUSSANLEGG KLOPPAVEIEN 16 AS?

BUSSANLEGG KLOPPAVEIEN 16 AS had revenue of NOK 4.5m in 2025.

Where is BUSSANLEGG KLOPPAVEIEN 16 AS based?

BUSSANLEGG KLOPPAVEIEN 16 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.