BIZTRAC BETA
COMPANY REGISTER PROFILE
920872565 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Site preparation

KFM AS

Org. no. 920872565 Limited company (AS) Gjøvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 754,000
Operating profit NOK −9,000
Equity NOK −242,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−242k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9k kr).

KFM AS is registered as a limited company in Gjøvik, Innlandet with organisation number 920872565. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Maskinkjøring, reparasjon og montasje, samt alt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 754,000 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 754,000
Operating profit
NOK −9,000
Equity
NOK −242,000

Financial health · 2025

Liquidity
0.37
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-326.7%
Weak
Equity as a share of total capital

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

Who owns KFM AS?

KEN ROBIN FURUHEIM MIDTLIEN
KFM AS
NOK 754,000 rev. · NOK −9,000 profit

KFM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KFM AS

Who owns KFM AS?

KEN ROBIN FURUHEIM MIDTLIEN is the largest registered owner, with 100.0%.

What is the revenue of KFM AS?

KFM AS had revenue of NOK 754,000 in 2025.

Who is the general manager of KFM AS?

Ken Robin Furuheim Midtlien is registered as general manager of KFM AS.

Where is KFM AS based?

KFM AS has its business address in Bybrua.

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.