BIZTRAC BETA
Wholesale of other food

KOBUK AS

Org. no. 971191635 Limited company (AS) Grimstad Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 242,000
Operating profit NOK −22,000
Equity NOK 272,000
Incorporated 1994
Share capital NOK 250,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−22k kr).

KOBUK AS is registered as a limited company in Grimstad, Agder with organisation number 971191635. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 1994. Registered share capital is NOK 250,000, divided into 10 shares. The company's stated purpose is: “Utvikling og distribusjon av produkter og tjenester relatert til kjæledyr og dets eiere, tjenester relatert til prosjektutvikling og bedriftsledelse, informasjons- og publiseringstjenester. Kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 242,000 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 242,000
Operating profit
NOK −22,000
Equity
NOK 272,000
Est. value
NOK 147,000

Financial health · 2024

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

Who owns KOBUK AS?

STIG MARTHINSEN
KOBUK AS
NOK 242,000 rev. · NOK −22,000 profit

KOBUK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KOBUK AS

Who owns KOBUK AS?

STIG MARTHINSEN is the largest registered owner, with 100.0%.

What is the revenue of KOBUK AS?

KOBUK AS had revenue of NOK 242,000 in 2024.

Who is the general manager of KOBUK AS?

Stig Marthinsen is registered as general manager of KOBUK AS.

Where is KOBUK AS based?

KOBUK AS has its business address in Grimstad.

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.