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

HULLEBERG MASKIN AS

Org. no. 897885492 Limited company (AS) Ringsaker Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 26.8m
Operating profit NOK 313,000
Equity NOK 6.0m
Incorporated 2012
Employees 22
Share capital NOK 66,000

HULLEBERG MASKIN AS is registered as a limited company in Ringsaker, Innlandet with organisation number 897885492. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2012 and has 22 registered employees. Registered share capital is NOK 66,000, divided into 66 shares. The company's stated purpose is: “Entreprnør innen graving, transport og det som naturlig tilhører denne virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.8m in revenue and NOK 313,000 in operating profit.

Key figures · 2025

Revenue
NOK 26.8m
▼ −0 %
Operating profit
NOK 313,000
▼ −89 %
Equity
NOK 6.0m
▲ +2 %
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
1.6%
Weak
Return on total assets
Solidity
21.0%
Good
Equity as a share of total capital

Who owns HULLEBERG MASKIN AS?

HULLEBERG MASKIN AS
NOK 26.8m rev. · NOK 313,000 profit

HULLEBERG MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HULLEBERG MASKIN AS

Who owns HULLEBERG MASKIN AS?

GAUPEN HOLDING AS is the largest registered owner, with 54.5%.

What is the revenue of HULLEBERG MASKIN AS?

HULLEBERG MASKIN AS had revenue of NOK 26.8m in 2025.

Who is the general manager of HULLEBERG MASKIN AS?

John Alex Hulleberg is registered as general manager of HULLEBERG MASKIN AS.

Where is HULLEBERG MASKIN AS based?

HULLEBERG MASKIN AS has its business address in Næroset.

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.