BIZTRAC BETA
Activities of fitness centres

ÅMOT FYSIKALSKE AS

Org. no. 979925441 Limited company (AS) Modum Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 589,000
Equity NOK 1.5m
Incorporated 1998
Employees 7
Share capital NOK 100,000

ÅMOT FYSIKALSKE AS is registered as a limited company in Modum, Buskerud with organisation number 979925441. The business is classified under activities of fitness centres (NACE 93.130). The company was incorporated in 1998 and has 7 registered employees. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Å drive treningsstudio og utleie av lokaler til selvstendig næringsdrivende fysioterapeuter, samt hva hermed står i forbindelse, kjøp og salg av fast eiendom, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 589,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 589,000
Equity
NOK 1.5m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns ÅMOT FYSIKALSKE AS?

MARTINE HEIDUM-ZIEGLER
ÅMOT FYSIKALSKE AS
NOK 3.1m rev. · NOK 589,000 profit

ÅMOT FYSIKALSKE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ÅMOT FYSIKALSKE AS

Who owns ÅMOT FYSIKALSKE AS?

MARTINE HEIDUM-ZIEGLER is the largest registered owner, with 50.0%.

What is the revenue of ÅMOT FYSIKALSKE AS?

ÅMOT FYSIKALSKE AS had revenue of NOK 3.1m in 2025.

Who is the general manager of ÅMOT FYSIKALSKE AS?

Tiril Vangen is registered as general manager of ÅMOT FYSIKALSKE AS.

Where is ÅMOT FYSIKALSKE AS based?

ÅMOT FYSIKALSKE 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.