BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

TBM MASKIN AS

Org. no. 824382182 Limited company (AS) Ullensvang Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 9.9m
Operating profit NOK 1.7m
Equity NOK 3.6m
Incorporated 2019
Share capital NOK 2.0m

TBM MASKIN AS is registered as a limited company in Ullensvang, Vestland with organisation number 824382182. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2019. Registered share capital is NOK 2.0m, divided into 23565 shares. The company's stated purpose is: “Investere i maskinpark til anleggsbransjen og drive utleie av maskiner.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.9m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 9.9m
Operating profit
NOK 1.7m
Equity
NOK 3.6m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns TBM MASKIN AS?

TE KVALVIK HOLDING AS
TBM MASKIN AS
NOK 9.9m rev. · NOK 1.7m profit

TBM MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TBM MASKIN AS own?

TBM MASKIN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TBM MASKIN AS

Who owns TBM MASKIN AS?

TE KVALVIK HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of TBM MASKIN AS?

TBM MASKIN AS had revenue of NOK 9.9m in 2024.

Who is the general manager of TBM MASKIN AS?

Arne Dyngeland is registered as general manager of TBM MASKIN AS.

Where is TBM MASKIN AS based?

TBM MASKIN AS has its business address in Utne.

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.