biztrac. BETA
COMPANY REGISTER PROFILE
917697698 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Event catering activities

KOLBOTN GRILL AS

Org. no. 917697698 Limited company (AS) Nordre Follo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 7.9m
Operating profit NOK 451,000
Equity NOK 746,000
Incorporated 2016
Employees 7
Share capital NOK 30,000

KOLBOTN GRILL AS is registered as a limited company in Nordre Follo, Akershus with organisation number 917697698. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2016 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive catering og take away i restaurant bransje samt annet som naturlig står i den forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK 451,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.9m
▲ +18 %
Operating profit
NOK 451,000
▼ −16 %
Equity
NOK 746,000
▲ +102 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
1.72
Good
Current assets ÷ current liabilities
Profitability
32.8%
Very good
Return on total assets
Solidity
47.5%
Very good
Equity as a share of total capital

Who owns KOLBOTN GRILL AS?

KOLBOTN GRILL AS
NOK 7.9m rev. · NOK 451,000 profit

KOLBOTN GRILL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOLBOTN GRILL AS

Who owns KOLBOTN GRILL AS?

Abdullah Demirez is the largest registered owner, with 100.0%.

What is the revenue of KOLBOTN GRILL AS?

KOLBOTN GRILL AS had revenue of NOK 7.9m in 2025.

Who is the general manager of KOLBOTN GRILL AS?

Abdullah Demirez is registered as general manager of KOLBOTN GRILL AS.

Where is KOLBOTN GRILL AS based?

KOLBOTN GRILL AS has its business address in Kolbotn.

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.