BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

TROFORS BYGGEMONTERING AS

Org. no. 924533269 Limited company (AS) Grane Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 12.2m
Operating profit NOK 336,000
Equity NOK 3.3m
Incorporated 2020
Share capital NOK 400,000

TROFORS BYGGEMONTERING AS is registered as a limited company in Grane, Nordland with organisation number 924533269. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2020. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Takstolproduksjon, salg av byggevarer og alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.2m in revenue and NOK 336,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.2m
Operating profit
NOK 336,000
Equity
NOK 3.3m
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
3.64
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
64.8%
Very good
Equity as a share of total capital

Who owns TROFORS BYGGEMONTERING AS?

ØKO HOLDING AS
TROFORS BYGGEMONTERING AS
NOK 12.2m rev. · NOK 336,000 profit

TROFORS BYGGEMONTERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROFORS BYGGEMONTERING AS

Who owns TROFORS BYGGEMONTERING AS?

ØKO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of TROFORS BYGGEMONTERING AS?

TROFORS BYGGEMONTERING AS had revenue of NOK 12.2m in 2025.

Who is the general manager of TROFORS BYGGEMONTERING AS?

Øystein Kolberg Olsen is registered as general manager of TROFORS BYGGEMONTERING AS.

Where is TROFORS BYGGEMONTERING AS based?

TROFORS BYGGEMONTERING AS has its business address in Trofors.

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.