BIZTRAC BETA
General medical practice activities

FETSUND LEGEKONTOR AS

Org. no. 980762769 Limited company (AS) Lillestrøm Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −2,000
Equity NOK 275,000
Incorporated 1999
Share capital NOK 100,000

Signals

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

FETSUND LEGEKONTOR AS is registered as a limited company in Lillestrøm, Akershus with organisation number 980762769. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 1999. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Legevirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK −2,000
Equity
NOK 275,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns FETSUND LEGEKONTOR AS?

ZEWENGHIL GHEBRESELASSIE TESFAGHABR
FETSUND LEGEKONTOR AS
NOK 2.5m rev. · NOK −2,000 profit

FETSUND LEGEKONTOR AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FETSUND LEGEKONTOR AS

Who owns FETSUND LEGEKONTOR AS?

ZEWENGHIL GHEBRESELASSIE TESFAGHABR is the largest registered owner, with 50.0%.

What is the revenue of FETSUND LEGEKONTOR AS?

FETSUND LEGEKONTOR AS had revenue of NOK 2.5m in 2025.

Who is the general manager of FETSUND LEGEKONTOR AS?

Rannveig Berglund is registered as general manager of FETSUND LEGEKONTOR AS.

Where is FETSUND LEGEKONTOR AS based?

FETSUND LEGEKONTOR AS has its business address in Fetsund.

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.