biztrac. BETA
COMPANY REGISTER PROFILE
926156861 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of dairy products

OSTEPRODUKSJON AS

Org. no. 926156861 Limited company (AS) Klepp Incorporated 2020 Active
Revenue 2025 NOK 798,000
Operating profit NOK −99,000
Equity NOK −204,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−204k kr).

OSTEPRODUKSJON AS is registered as a limited company in Klepp, Rogaland with organisation number 926156861. The business is classified under manufacture of dairy products (NACE 10.510). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10000 shares. The company's stated purpose is: “Produsjon av næringsmidler, osteproduksjon.”. The most recent filed accounts, for the 2025 financial year, show NOK 798,000 in revenue and NOK −99,000 in operating profit.

Key figures · 2025

Revenue
NOK 798,000
▼ −39 %
Operating profit
NOK −99,000
▲ +20 %
Equity
NOK −204,000
▼ −124 %

Financial health · 2025

Liquidity
0.48
Not satisfactory
Current assets ÷ current liabilities
Profitability
-46.0%
Not satisfactory
Return on total assets
Solidity
-108.2%
Weak
Equity as a share of total capital

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

Who owns OSTEPRODUKSJON AS?

OSTEPRODUKSJON AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSTEPRODUKSJON AS

Who owns OSTEPRODUKSJON AS?

Hanna Voll Kjøllesdal is the largest registered owner, with 50.0%.

What is the revenue of OSTEPRODUKSJON AS?

OSTEPRODUKSJON AS had revenue of NOK 798,000 in 2025.

Who is the general manager of OSTEPRODUKSJON AS?

Ingvar Kjøllesdal is registered as general manager of OSTEPRODUKSJON AS.

Where is OSTEPRODUKSJON AS based?

OSTEPRODUKSJON AS has its business address in Voll.

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.