BIZTRAC BETA
General medical practice activities

KLØFTA LEGESENTER AS

Org. no. 978629857 Limited company (AS) Ullensaker Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 5.4m
Operating profit NOK −372,000
Equity NOK 515,000
Incorporated 1997
Employees 7
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−372k kr).

KLØFTA LEGESENTER AS is registered as a limited company in Ullensaker, Akershus with organisation number 978629857. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 1997 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 300 shares. The company's stated purpose is: “Legesenter og hva som herav naturlig står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.4m in revenue and NOK −372,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.4m
Operating profit
NOK −372,000
Equity
NOK 515,000
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns KLØFTA LEGESENTER AS?

CATHRINE TØLLØFSRUD
KLØFTA LEGESENTER AS
NOK 5.4m rev. · NOK −372,000 profit

KLØFTA LEGESENTER AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLØFTA LEGESENTER AS

Who owns KLØFTA LEGESENTER AS?

CATHRINE TØLLØFSRUD is the largest registered owner, with 14.3%.

What is the revenue of KLØFTA LEGESENTER AS?

KLØFTA LEGESENTER AS had revenue of NOK 5.4m in 2025.

Who is the general manager of KLØFTA LEGESENTER AS?

Espen Madsen Devold is registered as general manager of KLØFTA LEGESENTER AS.

Where is KLØFTA LEGESENTER AS based?

KLØFTA LEGESENTER AS has its business address in Kløfta.

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.