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

GULLBRÅ MASKIN AS

Org. no. 917959234 Limited company (AS) Vaksdal Incorporated 2016 Active
Revenue 2025 NOK 1.9m
Operating profit NOK 94,000
Equity NOK 0
Incorporated 2016
Share capital NOK 30,000

GULLBRÅ MASKIN AS is registered as a limited company in Vaksdal, Vestland with organisation number 917959234. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Anleggsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 94,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
▲ +41 %
Operating profit
NOK 94,000
▲ +143 %
Equity
NOK 0
▼ −100 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
0.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GULLBRÅ MASKIN AS?

GULLBRÅ MASKIN AS
NOK 1.9m rev. · NOK 94,000 profit

GULLBRÅ MASKIN AS has 2 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2022.

All shareholders and roles →

Frequently asked questions about GULLBRÅ MASKIN AS

Who owns GULLBRÅ MASKIN AS?

Eldbjørg Irene Gullbrå is the largest registered owner, with 90.0%.

What is the revenue of GULLBRÅ MASKIN AS?

GULLBRÅ MASKIN AS had revenue of NOK 1.9m in 2025.

Who is the general manager of GULLBRÅ MASKIN AS?

Hans Egil Gullbrå is registered as general manager of GULLBRÅ MASKIN AS.

Where is GULLBRÅ MASKIN AS based?

GULLBRÅ MASKIN AS has its business address in Eidslandet.

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.