BIZTRAC BETA
Wholesale of other machinery and equipment

APS HOLDING AS

Org. no. 991949666 Limited company (AS) Melhus Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −33,000
Equity NOK 2.7m
Incorporated 2007
Share capital NOK 6.7m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−33k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

APS HOLDING AS is registered as a limited company in Melhus, Trøndelag with organisation number 991949666. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2007. Registered share capital is NOK 6.7m, divided into 6700 shares. The company's stated purpose is: “Drive med aksjeinvesteringer og investeringer i og utleie av anlegg og utstyr, samt hva dermed står i forbindelse med, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −33,000
Equity
NOK 2.7m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns APS HOLDING AS?

FRODE MASTAD HOLDING AS
APS HOLDING AS
· NOK −33,000 profit

APS HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does APS HOLDING AS own?

APS HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about APS HOLDING AS

Who owns APS HOLDING AS?

FRODE MASTAD HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of APS HOLDING AS?

Roar Johnny Burø is registered as general manager of APS HOLDING AS.

Where is APS HOLDING AS based?

APS HOLDING AS has its business address in Melhus.

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.