biztrac. BETA
COMPANY REGISTER PROFILE
930340553 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Combined facilities support activities

STRAUMSØY MASKIN AS

Org. no. 930340553 Limited company (AS) Ullensvang Incorporated 2022 Active
Revenue 2025 NOK 1.8m
Operating profit NOK 79,000
Equity NOK 549,000
Incorporated 2022
Share capital NOK 110,000

STRAUMSØY MASKIN AS is registered as a limited company in Ullensvang, Vestland with organisation number 930340553. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2022. Registered share capital is NOK 110,000, divided into 110 shares. The company's stated purpose is: “Vaktmestertjenester. Utleie av sjåfør og grunnarbeid, industrivedlikehold, ved og skogrydding, utleie av diverse maskiner, vintervedlikehold, salg av tjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 79,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
▲ +43 %
Operating profit
NOK 79,000
▼ −76 %
Equity
NOK 549,000
▲ +14 %
Est. value
NOK 802,000

Financial health · 2025

Liquidity
2.55
Very good
Current assets ÷ current liabilities
Profitability
10.7%
Good
Return on total assets
Solidity
72.7%
Very good
Equity as a share of total capital

Who owns STRAUMSØY MASKIN AS?

STRAUMSØY MASKIN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about STRAUMSØY MASKIN AS

Who owns STRAUMSØY MASKIN AS?

Harald Straumsøy is the largest registered owner, with 33.6%.

What is the revenue of STRAUMSØY MASKIN AS?

STRAUMSØY MASKIN AS had revenue of NOK 1.8m in 2025.

Who is the general manager of STRAUMSØY MASKIN AS?

Harald Straumsøy is registered as general manager of STRAUMSØY MASKIN AS.

Where is STRAUMSØY MASKIN AS based?

STRAUMSØY MASKIN AS has its business address in Skare.

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.