BIZTRAC BETA
Physiotherapy activities

ÅMLI FYSIOTERAPI & TRENING AS

Org. no. 998244471 Limited company (AS) Åmli Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 405,000
Equity NOK 2.0m
Incorporated 2012
Share capital NOK 30,000

ÅMLI FYSIOTERAPI & TRENING AS is registered as a limited company in Åmli, Agder with organisation number 998244471. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Treningssenter, salg av fysioterapitjenester og andre produkter/tjenester som hører naturlig sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 405,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 405,000
Equity
NOK 2.0m
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns ÅMLI FYSIOTERAPI & TRENING AS?

MERETE FOGH LUND
ÅMLI FYSIOTERAPI & TRENING AS
NOK 1.9m rev. · NOK 405,000 profit

ÅMLI FYSIOTERAPI & TRENING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅMLI FYSIOTERAPI & TRENING AS

Who owns ÅMLI FYSIOTERAPI & TRENING AS?

MERETE FOGH LUND is the largest registered owner, with 100.0%.

What is the revenue of ÅMLI FYSIOTERAPI & TRENING AS?

ÅMLI FYSIOTERAPI & TRENING AS had revenue of NOK 1.9m in 2025.

Who is the general manager of ÅMLI FYSIOTERAPI & TRENING AS?

Merete Fogh Lund is registered as general manager of ÅMLI FYSIOTERAPI & TRENING AS.

Where is ÅMLI FYSIOTERAPI & TRENING AS based?

ÅMLI FYSIOTERAPI & TRENING AS has its business address in Åmli.

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.