BIZTRAC BETA
Rental and operating of own or leased real estate

EIKRINGEN 19 OG 20 AS

Org. no. 915096158 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 12.6m
Operating profit NOK 8.5m
Equity NOK 19.9m
Incorporated 2015
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.

EIKRINGEN 19 OG 20 AS is registered as a limited company in Oslo, Oslo with organisation number 915096158. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 1.0m, divided into 1000000 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 12.6m in revenue and NOK 8.5m in operating profit.

Key figures · 2025

Revenue
NOK 12.6m
Operating profit
NOK 8.5m
Equity
NOK 19.9m
Est. value
NOK 23.2m

Financial health · 2025

Liquidity
0.32
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.6%
Satisfactory
Equity as a share of total capital

Who owns EIKRINGEN 19 OG 20 AS?

KOBBERVIKDALEN VERKSTEDSEIENDOM AS
EIKRINGEN 19 OG 20 AS
NOK 12.6m rev. · NOK 8.5m profit

EIKRINGEN 19 OG 20 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIKRINGEN 19 OG 20 AS

Who owns EIKRINGEN 19 OG 20 AS?

KOBBERVIKDALEN VERKSTEDSEIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of EIKRINGEN 19 OG 20 AS?

EIKRINGEN 19 OG 20 AS had revenue of NOK 12.6m in 2025.

Where is EIKRINGEN 19 OG 20 AS based?

EIKRINGEN 19 OG 20 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.