BIZTRAC BETA
Restaurant activities

VINTAGE KITCHEN AS

Org. no. 918757163 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 9.2m
Operating profit NOK 390,000
Equity NOK 711,000
Incorporated 2017
Employees 15
Share capital NOK 500,000

VINTAGE KITCHEN AS is registered as a limited company in Oslo, Oslo with organisation number 918757163. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 15 registered employees. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Restaurantvirksomhet, catering, investering i fast eiendom og verdipapirer, import av vin, kursvirksomhet og deltagelse i andre selskaper tilknyttet restaurantvirksomheten.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.2m in revenue and NOK 390,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.2m
Operating profit
NOK 390,000
Equity
NOK 711,000
Est. value
NOK 1.3m

Financial health · 2024

Liquidity
2.23
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.4%
Satisfactory
Equity as a share of total capital

Who owns VINTAGE KITCHEN AS?

HEINI KJÆRGAARD PETERSEN
VINTAGE KITCHEN AS
NOK 9.2m rev. · NOK 390,000 profit

VINTAGE KITCHEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINTAGE KITCHEN AS

Who owns VINTAGE KITCHEN AS?

HEINI KJÆRGAARD PETERSEN is the largest registered owner, with 100.0%.

What is the revenue of VINTAGE KITCHEN AS?

VINTAGE KITCHEN AS had revenue of NOK 9.2m in 2024.

Who is the general manager of VINTAGE KITCHEN AS?

Heini Kjærgaard Petersen is registered as general manager of VINTAGE KITCHEN AS.

Where is VINTAGE KITCHEN AS based?

VINTAGE KITCHEN 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.