BIZTRAC BETA
Rental and operating of own or leased real estate

ASTO AS

Org. no. 988433608 Limited company (AS) Lillehammer Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 34.4m
Operating profit NOK 23.6m
Equity NOK 70.4m
Incorporated 2005
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ASTO AS is registered as a limited company in Lillehammer, Innlandet with organisation number 988433608. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 10100 shares. The company's stated purpose is: “Eie og forestå drift av forretningseiendommer samt tilknyttet næringsvirksomhet og annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.4m in revenue and NOK 23.6m in operating profit.

Key figures · 2024

Revenue
NOK 34.4m
Operating profit
NOK 23.6m
Equity
NOK 70.4m
Est. value
NOK 92.9m

Financial health · 2024

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

Who owns ASTO AS?

SEIELSTAD HOLDING AS
ASTO AS
NOK 34.4m rev. · NOK 23.6m profit

ASTO AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ASTO AS er morselskap for 5 datterselskaper:

Frequently asked questions about ASTO AS

Who owns ASTO AS?

SEIELSTAD HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ASTO AS?

ASTO AS had revenue of NOK 34.4m in 2024.

Who is the general manager of ASTO AS?

Åge Erling Melbø is registered as general manager of ASTO AS.

Where is ASTO AS based?

ASTO AS has its business address in Lillehammer.

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.