BIZTRAC BETA
Event catering activities

KOKER & LOKER AS

Org. no. 922750955 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 122,000
Operating profit NOK 27,000
Equity NOK 95,000
Incorporated 2019
Share capital NOK 30,000

KOKER & LOKER AS is registered as a limited company in Bergen, Vestland with organisation number 922750955. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Cateringvirksomhet, servering ved events og annen arrangementer samt tilhørende virksomhet. Selskapet kan og eie aksjer og andeler i selskapet som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 122,000 in revenue and NOK 27,000 in operating profit.

Key figures · 2024

Revenue
NOK 122,000
Operating profit
NOK 27,000
Equity
NOK 95,000
Est. value
NOK 145,000

Financial health · 2024

Liquidity
4.53
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
77.9%
Weak
Equity as a share of total capital

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

Who owns KOKER & LOKER AS?

NIKOLAI KJEILEN NYGAARD
KOKER & LOKER AS
NOK 122,000 rev. · NOK 27,000 profit

KOKER & LOKER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOKER & LOKER AS

Who owns KOKER & LOKER AS?

NIKOLAI KJEILEN NYGAARD is the largest registered owner, with 50.0%.

What is the revenue of KOKER & LOKER AS?

KOKER & LOKER AS had revenue of NOK 122,000 in 2024.

Who is the general manager of KOKER & LOKER AS?

Hans Jørgen Monsen is registered as general manager of KOKER & LOKER AS.

Where is KOKER & LOKER AS based?

KOKER & LOKER AS has its business address in Bergen.

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.