BIZTRAC BETA
Restaurant activities

GLADKJØKKENET AS

Org. no. 915475701 Limited company (AS) Vennesla Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 1.9m
Equity NOK 827,000
Incorporated 2015
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.

GLADKJØKKENET AS is registered as a limited company in Vennesla, Agder with organisation number 915475701. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kurs i matlaging, drift av restaurant, kjøkken, salg av mat og drikke og alt som naturlig hører inn under dette. Samt delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 1.9m
Equity
NOK 827,000
Est. value
NOK 5.7m

Financial health · 2024

Liquidity
1.34
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.4%
Good
Equity as a share of total capital

Who owns GLADKJØKKENET AS?

NÆRINGS INVEST AS
GLADKJØKKENET AS
NOK 4.2m rev. · NOK 1.9m profit

GLADKJØKKENET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GLADKJØKKENET AS

Who owns GLADKJØKKENET AS?

NÆRINGS INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of GLADKJØKKENET AS?

GLADKJØKKENET AS had revenue of NOK 4.2m in 2024.

Where is GLADKJØKKENET AS based?

GLADKJØKKENET AS has its business address in Vennesla.

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.