BIZTRAC BETA
Repair and maintenance of machinery

MASKINIA HOLDING AS

Org. no. 992360240 Limited company (AS) Porsgrunn Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −794,000
Equity NOK 152.3m
Incorporated 2008
Share capital NOK 3.3m

Signals

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

MASKINIA HOLDING AS is registered as a limited company in Porsgrunn, Telemark with organisation number 992360240. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2008. Registered share capital is NOK 3.3m, divided into 3268838 shares. The company's stated purpose is: “Handel med og investering i verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −794,000
Equity
NOK 152.3m
Est. value
NOK 130.6m

Financial health · 2025

Liquidity
1.65
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.6%
Good
Equity as a share of total capital

Who owns MASKINIA HOLDING AS?

REITEN & CO CAPITAL PARTNERS VI
MASKINIA HOLDING AS
· NOK −794,000 profit

MASKINIA HOLDING AS has 10 registered shareholders:

All shareholders and roles →

Which companies does MASKINIA HOLDING AS own?

MASKINIA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about MASKINIA HOLDING AS

Who owns MASKINIA HOLDING AS?

REITEN & CO CAPITAL PARTNERS VI is the largest registered owner, with 86.8%.

Who is the general manager of MASKINIA HOLDING AS?

Anders Henni is registered as general manager of MASKINIA HOLDING AS.

Where is MASKINIA HOLDING AS based?

MASKINIA HOLDING AS has its business address in Porsgrunn.

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.