BIZTRAC BETA
General medical practice activities

AKERSHUS LEGESENTER AS

Org. no. 921151551 Limited company (AS) Lørenskog Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 81
Equity NOK −42,000
Incorporated 2018
Share capital NOK 40,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−42k kr).

AKERSHUS LEGESENTER AS is registered as a limited company in Lørenskog, Akershus with organisation number 921151551. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2018. Registered share capital is NOK 40,000, divided into 40000 shares. The company's stated purpose is: “å drive legesentervirksomhet med alt det innebærer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 81 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 81
Equity
NOK −42,000
Est. value
NOK 620

Financial health · 2025

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

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

Who owns AKERSHUS LEGESENTER AS?

HIRA AFTAB
AKERSHUS LEGESENTER AS
NOK 1.9m rev. · NOK 81 profit

AKERSHUS LEGESENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AKERSHUS LEGESENTER AS

Who owns AKERSHUS LEGESENTER AS?

HIRA AFTAB is the largest registered owner, with 33.3%.

What is the revenue of AKERSHUS LEGESENTER AS?

AKERSHUS LEGESENTER AS had revenue of NOK 1.9m in 2025.

Who is the general manager of AKERSHUS LEGESENTER AS?

Ragnar Tønsberg is registered as general manager of AKERSHUS LEGESENTER AS.

Where is AKERSHUS LEGESENTER AS based?

AKERSHUS LEGESENTER AS has its business address in Lørenskog.

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.