BIZTRAC BETA
General medical practice activities

ÅMOT LEGEPRAKSIS AS

Org. no. 913039068 Limited company (AS) Modum Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK 441,000
Equity NOK 1.5m
Incorporated 2013
Share capital NOK 30,000

ÅMOT LEGEPRAKSIS AS is registered as a limited company in Modum, Buskerud with organisation number 913039068. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive allmennlege praksis som innebærer klinisk og administrativt arbeid for befolkning med behov for fastlege hjelp. I tillegg evt. oppgaver som hører til i fastlegeordningen og som er en del av førstelinje helsetjenesten i kommunen.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK 441,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK 441,000
Equity
NOK 1.5m
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns ÅMOT LEGEPRAKSIS AS?

ALI RAZA
ÅMOT LEGEPRAKSIS AS
NOK 4.0m rev. · NOK 441,000 profit

ÅMOT LEGEPRAKSIS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅMOT LEGEPRAKSIS AS

Who owns ÅMOT LEGEPRAKSIS AS?

ALI RAZA is the largest registered owner, with 100.0%.

What is the revenue of ÅMOT LEGEPRAKSIS AS?

ÅMOT LEGEPRAKSIS AS had revenue of NOK 4.0m in 2025.

Who is the general manager of ÅMOT LEGEPRAKSIS AS?

Ali Raza is registered as general manager of ÅMOT LEGEPRAKSIS AS.

Where is ÅMOT LEGEPRAKSIS AS based?

ÅMOT LEGEPRAKSIS AS has its business address in Åmot.

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.