BIZTRAC BETA
Other health services

EXPIRO AS

Org. no. 911678020 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK 554,000
Equity NOK 1.5m
Incorporated 2013
Share capital NOK 30,000

EXPIRO AS is registered as a limited company in Oslo, Oslo with organisation number 911678020. The business is classified under other health services (NACE 86.993). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Forestå tjenester innen helsebringende aktiviteter og personlig utvikling. Konsulenttjenester innen helsebringende aktiviteter og andre konsulenttjenester i tilknytning til personlig utvikling. Deltakelse i andre selskaper. Kjøp og salg, samt utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK 554,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK 554,000
Equity
NOK 1.5m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns EXPIRO AS?

OLE-ARVID LIODDEN
EXPIRO AS
NOK 2.4m rev. · NOK 554,000 profit

EXPIRO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EXPIRO AS own?

EXPIRO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about EXPIRO AS

Who owns EXPIRO AS?

OLE-ARVID LIODDEN is the largest registered owner, with 100.0%.

What is the revenue of EXPIRO AS?

EXPIRO AS had revenue of NOK 2.4m in 2024.

Who is the general manager of EXPIRO AS?

Ole-Arvid Liodden is registered as general manager of EXPIRO AS.

Where is EXPIRO AS based?

EXPIRO AS has its business address in Oslo.

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.