BIZTRAC BETA
Restaurant activities

KÖD FROGNER AS

Org. no. 826763132 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 19.9m
Operating profit NOK 981,000
Equity NOK 929,000
Incorporated 2021
Employees 46
Share capital NOK 30,000

Signals

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

KÖD FROGNER AS is registered as a limited company in Oslo, Oslo with organisation number 826763132. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021 and has 46 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Restaurantvirksomhet, samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.9m in revenue and NOK 981,000 in operating profit.

Key figures · 2024

Revenue
NOK 19.9m
Operating profit
NOK 981,000
Equity
NOK 929,000
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns KÖD FROGNER AS?

DININGSIX NORGE HOLDING AS
KÖD FROGNER AS
NOK 19.9m rev. · NOK 981,000 profit

KÖD FROGNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KÖD FROGNER AS

Who owns KÖD FROGNER AS?

DININGSIX NORGE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of KÖD FROGNER AS?

KÖD FROGNER AS had revenue of NOK 19.9m in 2024.

Who is the general manager of KÖD FROGNER AS?

Lasse Juul Horn is registered as general manager of KÖD FROGNER AS.

Where is KÖD FROGNER AS based?

KÖD FROGNER 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.