BIZTRAC BETA
Restaurant activities

KVÅL GRILLEN AS

Org. no. 827301272 Limited company (AS) Melhus Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK −14,000
Equity NOK −334,000
Incorporated 2021
Employees 5
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−334k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).

KVÅL GRILLEN AS is registered as a limited company in Melhus, Trøndelag with organisation number 827301272. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift av restaurant og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK −14,000
Equity
NOK −334,000

Financial health · 2025

Liquidity
0.75
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-62.9%
Weak
Equity as a share of total capital

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

Who owns KVÅL GRILLEN AS?

DENIZ CELIK
KVÅL GRILLEN AS
NOK 4.0m rev. · NOK −14,000 profit

KVÅL GRILLEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVÅL GRILLEN AS

Who owns KVÅL GRILLEN AS?

DENIZ CELIK is the largest registered owner, with 100.0%.

What is the revenue of KVÅL GRILLEN AS?

KVÅL GRILLEN AS had revenue of NOK 4.0m in 2025.

Who is the general manager of KVÅL GRILLEN AS?

Deniz Celik is registered as general manager of KVÅL GRILLEN AS.

Where is KVÅL GRILLEN AS based?

KVÅL GRILLEN AS has its business address in Kvål.

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.