BIZTRAC BETA
Site preparation

FRANK HOLE MASKIN AS

Org. no. 916498055 Limited company (AS) Sykkylven Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK −163,000
Equity NOK 470,000
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−163k kr).

FRANK HOLE MASKIN AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 916498055. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Graving og transport samt hva som er naturlig i den forbindelse. Herunder investeringer i andre selskap med tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −163,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.5m
Operating profit
NOK −163,000
Equity
NOK 470,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns FRANK HOLE MASKIN AS?

FRANK HOLE
FRANK HOLE MASKIN AS
NOK 2.5m rev. · NOK −163,000 profit

FRANK HOLE MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRANK HOLE MASKIN AS

Who owns FRANK HOLE MASKIN AS?

FRANK HOLE is the largest registered owner, with 100.0%.

What is the revenue of FRANK HOLE MASKIN AS?

FRANK HOLE MASKIN AS had revenue of NOK 2.5m in 2025.

Who is the general manager of FRANK HOLE MASKIN AS?

Frank Hole is registered as general manager of FRANK HOLE MASKIN AS.

Where is FRANK HOLE MASKIN AS based?

FRANK HOLE MASKIN AS has its business address in Straumgjerde.

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.