biztrac. BETA
COMPANY REGISTER PROFILE
921996845 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

REIERLIEN MASKIN AS

Org. no. 921996845 Limited company (AS) Hustadvika Incorporated 2018 Active
Revenue 2025 NOK 177,000
Operating profit NOK 21,000
Equity NOK 157,000
Incorporated 2018
Share capital NOK 30,000

REIERLIEN MASKIN AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 921996845. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive maskinentreprenørvirksomhet, samt det som står i forbindelse med dette, herunder å delta i selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 177,000 in revenue and NOK 21,000 in operating profit.

Key figures · 2025

Revenue
NOK 177,000
▼ −25 %
Operating profit
NOK 21,000
▲ +255 %
Equity
NOK 157,000
▼ −90 %
Est. value
NOK 156,000

Financial health · 2025

Liquidity
0.78
Weak
Current assets ÷ current liabilities
Profitability
2.0%
Weak
Return on total assets
Solidity
68.3%
Very good
Equity as a share of total capital

Who owns REIERLIEN MASKIN AS?

REIERLIEN MASKIN AS
NOK 177,000 rev. · NOK 21,000 profit

REIERLIEN MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about REIERLIEN MASKIN AS

Who owns REIERLIEN MASKIN AS?

Arnt-Erik Hemme Lien is the largest registered owner, with 80.0%.

What is the revenue of REIERLIEN MASKIN AS?

REIERLIEN MASKIN AS had revenue of NOK 177,000 in 2025.

Who is the general manager of REIERLIEN MASKIN AS?

Arnt-Erik Hemme Lien is registered as general manager of REIERLIEN MASKIN AS.

Where is REIERLIEN MASKIN AS based?

REIERLIEN MASKIN AS has its business address in Eide.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.