BIZTRAC BETA
Construction of residential and non-residential buildings

BYÅSEN TREVARE AS

Org. no. 961393183 Limited company (AS) Trondheim Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 55.8m
Operating profit NOK 3.9m
Equity NOK 11.9m
Incorporated 1991
Employees 27
Share capital NOK 100,000

BYÅSEN TREVARE AS is registered as a limited company in Trondheim, Trøndelag with organisation number 961393183. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1991 and has 27 registered employees. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Håndverkertjenester, kjøp og salg, samt hva hermed står i forbindelse, herunder delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 55.8m in revenue and NOK 3.9m in operating profit.

Key figures · 2025

Revenue
NOK 55.8m
Operating profit
NOK 3.9m
Equity
NOK 11.9m
Est. value
NOK 19.5m

Financial health · 2025

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

Who owns BYÅSEN TREVARE AS?

BYÅSEN HOLDING AS
BYÅSEN TREVARE AS
NOK 55.8m rev. · NOK 3.9m profit

BYÅSEN TREVARE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYÅSEN TREVARE AS

Who owns BYÅSEN TREVARE AS?

BYÅSEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BYÅSEN TREVARE AS?

BYÅSEN TREVARE AS had revenue of NOK 55.8m in 2025.

Who is the general manager of BYÅSEN TREVARE AS?

Lars Ingvald Rognan Johansen is registered as general manager of BYÅSEN TREVARE AS.

Where is BYÅSEN TREVARE AS based?

BYÅSEN TREVARE AS has its business address in Heimdal.

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.