BIZTRAC BETA
Physiotherapy activities

ERIK HOLME AS

Org. no. 988719056 Limited company (AS) Moss Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 10,000
Operating profit NOK 5,000
Equity NOK 32,000
Incorporated 2005
Share capital NOK 100,000

ERIK HOLME AS is registered as a limited company in Moss, Østfold with organisation number 988719056. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Osteopati og fysioterapivirksomhet, finansforvaltning og drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 10,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 10,000
Operating profit
NOK 5,000
Equity
NOK 32,000
Est. value
NOK 41,000

Financial health · 2025

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

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

Who owns ERIK HOLME AS?

ERIK HOLME
ERIK HOLME AS
NOK 10,000 rev. · NOK 5,000 profit

ERIK HOLME AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERIK HOLME AS own?

ERIK HOLME AS holds a stake in 1 company:

See the full ownership structure →

Group structure

ERIK HOLME AS er morselskap for 1 datterselskap:

Frequently asked questions about ERIK HOLME AS

Who owns ERIK HOLME AS?

ERIK HOLME is the largest registered owner, with 100.0%.

What is the revenue of ERIK HOLME AS?

ERIK HOLME AS had revenue of NOK 10,000 in 2025.

Who is the general manager of ERIK HOLME AS?

Erik Holme is registered as general manager of ERIK HOLME AS.

Where is ERIK HOLME AS based?

ERIK HOLME AS has its business address in Dilling.

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.