BIZTRAC BETA
Retail sale of other new goods

EN KONGLE TIL AS

Org. no. 920847021 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK −47,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−47k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

EN KONGLE TIL AS is registered as a limited company in Oslo, Oslo with organisation number 920847021. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å selge egenproduserte, importerte og videreutviklede varer og tjenester. Selskapet skal søke å gjøre dette på en slik måte at det stimulerer til utvikling og læring av komersiell forståelse for barn og ungdom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK −47,000

Financial health · 2024

Liquidity
7.06
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-201.2%
Weak
Equity as a share of total capital

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

Who owns EN KONGLE TIL AS?

EN KONGLE AS
EN KONGLE TIL AS
NOK 0 rev. · NOK −12,000 profit

EN KONGLE TIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EN KONGLE TIL AS

Who owns EN KONGLE TIL AS?

EN KONGLE AS is the largest registered owner, with 100.0%.

What is the revenue of EN KONGLE TIL AS?

EN KONGLE TIL AS had revenue of NOK 0 in 2024.

Where is EN KONGLE TIL AS based?

EN KONGLE TIL 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.