BIZTRAC BETA
Manufacture of prepared meals and dishes

KOKERIET AS

Org. no. 932782731 Limited company (AS) Surnadal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 586,000
Operating profit NOK 213,000
Equity NOK 498,000
Incorporated 2023
Share capital NOK 30,000

KOKERIET AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 932782731. The business is classified under manufacture of prepared meals and dishes (NACE 10.850). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Produksjon og salg av grøt og trevarer og det som naturlig hører til. Samt å investere i aksjer og eiendom, og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 586,000 in revenue and NOK 213,000 in operating profit.

Key figures · 2025

Revenue
NOK 586,000
Operating profit
NOK 213,000
Equity
NOK 498,000
Est. value
NOK 963,000

Financial health · 2025

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

Who owns KOKERIET AS?

BJØRN SÆTERBØ
KOKERIET AS
NOK 586,000 rev. · NOK 213,000 profit

KOKERIET AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOKERIET AS

Who owns KOKERIET AS?

BJØRN SÆTERBØ is the largest registered owner, with 100.0%.

What is the revenue of KOKERIET AS?

KOKERIET AS had revenue of NOK 586,000 in 2025.

Who is the general manager of KOKERIET AS?

Bjørn Sæterbø is registered as general manager of KOKERIET AS.

Where is KOKERIET AS based?

KOKERIET AS has its business address in Surnadal.

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.