BIZTRAC BETA
Rental and operating of own or leased real estate

L16 SEKSJON 9 AS

Org. no. 935269164 Limited company (AS) Ringerike Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 52,000
Operating profit NOK 34,000
Equity NOK 51,000
Incorporated 2025
Share capital NOK 30,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-27 Adresseendring registrert 2026-06-27.

L16 SEKSJON 9 AS is registered as a limited company in Ringerike, Buskerud with organisation number 935269164. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie, utvikling og forvaltning av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 52,000 in revenue and NOK 34,000 in operating profit.

Key figures · 2025

Revenue
NOK 52,000
Operating profit
NOK 34,000
Equity
NOK 51,000
Est. value
NOK 112,000

Financial health · 2025

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns L16 SEKSJON 9 AS?

SG HOLDING 1 AS
L16 SEKSJON 9 AS
NOK 52,000 rev. · NOK 34,000 profit

L16 SEKSJON 9 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about L16 SEKSJON 9 AS

Who owns L16 SEKSJON 9 AS?

SG HOLDING 1 AS is the largest registered owner, with 100.0%.

What is the revenue of L16 SEKSJON 9 AS?

L16 SEKSJON 9 AS had revenue of NOK 52,000 in 2025.

Where is L16 SEKSJON 9 AS based?

L16 SEKSJON 9 AS has its business address in Hønefoss.

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.