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

MASKINTEKNIKK BERGEN AS

Org. no. 921560451 Limited company (AS) Bergen Incorporated 2018 Active
Revenue 2025 NOK 3.1m
Operating profit NOK 681,000
Equity NOK 1.9m
Incorporated 2018
Share capital NOK 30,000

MASKINTEKNIKK BERGEN AS is registered as a limited company in Bergen, Vestland with organisation number 921560451. 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 1000 shares. The company's stated purpose is: “Maskinentreprenør. Arbeid innen graving og grunnarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 681,000 in operating profit.

Former names: RIKTIG UTSTYR AS

Key figures · 2025

Revenue
NOK 3.1m
▲ +46 %
Operating profit
NOK 681,000
▲ +663 %
Equity
NOK 1.9m
▲ +31 %
Est. value
NOK 2.0m

Financial health · 2025

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
29.8%
Very good
Return on total assets
Solidity
71.2%
Very good
Equity as a share of total capital

Who owns MASKINTEKNIKK BERGEN AS?

MASKINTEKNIKK BERGEN AS
NOK 3.1m rev. · NOK 681,000 profit

MASKINTEKNIKK BERGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MASKINTEKNIKK BERGEN AS

Who owns MASKINTEKNIKK BERGEN AS?

Thorstein Størdal Gallefoss is the largest registered owner, with 100.0%.

What is the revenue of MASKINTEKNIKK BERGEN AS?

MASKINTEKNIKK BERGEN AS had revenue of NOK 3.1m in 2025.

Who is the general manager of MASKINTEKNIKK BERGEN AS?

Thorstein Størdal Gallefoss is registered as general manager of MASKINTEKNIKK BERGEN AS.

Where is MASKINTEKNIKK BERGEN AS based?

MASKINTEKNIKK BERGEN AS has its business address in Blomsterdalen.

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.