biztrac. BETA
COMPANY REGISTER PROFILE
911989484 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Retail sale of other new goods

EN KONGLE AS

Org. no. 911989484 Limited company (AS) Oslo Incorporated 2013 Active
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK −2.8m
Incorporated 2013
Share capital NOK 600,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,8 mill kr).

EN KONGLE AS is registered as a limited company in Oslo, Oslo with organisation number 911989484. The business is classified under retail sale of other new goods (NACE 47.780). The company was incorporated in 2013. Registered share capital is NOK 600,000, divided into 100000 shares. The company's stated purpose is: “Kjøp og salg av aksjer, fast eiendom og andre instrumenter, gjennom både passive og aktivt eierskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Former names: MØBO AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
▲ +75 %
Equity
NOK −2.8m
▲ +2 %

Financial health · 2025

Liquidity
23.40
Very good
Current assets ÷ current liabilities
Profitability
5.9%
Weak
Return on total assets
Solidity
-244.2%
Weak
Equity as a share of total capital

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

Who owns EN KONGLE AS?

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

EN KONGLE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does EN KONGLE AS own?

EN KONGLE AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about EN KONGLE AS

Who owns EN KONGLE AS?

OUG HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of EN KONGLE AS?

EN KONGLE AS had revenue of NOK 0 in 2025.

Where is EN KONGLE AS based?

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

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.