BIZTRAC BETA
Wholesale of agricultural machinery, equipment and supplies

KOFUKU AS

Org. no. 920168736 Limited company (AS) Frogn Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −41,000
Equity NOK 55,000
Incorporated 2017
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−41k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KOFUKU AS is registered as a limited company in Frogn, Akershus with organisation number 920168736. The business is classified under wholesale of agricultural machinery, equipment and supplies (NACE 46.610). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −41,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −41,000
Equity
NOK 55,000
Est. value
NOK 25.3m

Financial health · 2024

Liquidity
0.51
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
26.1%
Weak
Equity as a share of total capital

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

Who owns KOFUKU AS?

JAER GÅRD AS
KOFUKU AS
NOK 0 rev. · NOK −41,000 profit

KOFUKU AS has 3 registered shareholders:

All shareholders and roles →

Which companies does KOFUKU AS own?

KOFUKU AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KOFUKU AS

Who owns KOFUKU AS?

JAER GÅRD AS is the largest registered owner, with 33.3%.

What is the revenue of KOFUKU AS?

KOFUKU AS had revenue of NOK 0 in 2024.

Where is KOFUKU AS based?

KOFUKU AS has its business address in Nordre Frogn.

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.