BIZTRAC BETA
Joinery installation

TØMRERMESTER LYCHE & SIMONSEN AS

Org. no. 978670423 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 13.5m
Operating profit NOK 1.2m
Equity NOK 2.0m
Incorporated 1997
Employees 9
Share capital NOK 100,000

TØMRERMESTER LYCHE & SIMONSEN AS is registered as a limited company in Oslo, Oslo with organisation number 978670423. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 1997 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Hovedvekt på tømrer/snekkerarbeid og grunnarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 13.5m in revenue and NOK 1.2m in operating profit.

Key figures · 2025

Revenue
NOK 13.5m
Operating profit
NOK 1.2m
Equity
NOK 2.0m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns TØMRERMESTER LYCHE & SIMONSEN AS?

BJØRN GUNNAR LYCHE
TØMRERMESTER LYCHE & SIMONSEN AS
NOK 13.5m rev. · NOK 1.2m profit

TØMRERMESTER LYCHE & SIMONSEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TØMRERMESTER LYCHE & SIMONSEN AS

Who owns TØMRERMESTER LYCHE & SIMONSEN AS?

BJØRN GUNNAR LYCHE is the largest registered owner, with 75.0%.

What is the revenue of TØMRERMESTER LYCHE & SIMONSEN AS?

TØMRERMESTER LYCHE & SIMONSEN AS had revenue of NOK 13.5m in 2025.

Who is the general manager of TØMRERMESTER LYCHE & SIMONSEN AS?

Bjørn Gunnar Lyche is registered as general manager of TØMRERMESTER LYCHE & SIMONSEN AS.

Where is TØMRERMESTER LYCHE & SIMONSEN AS based?

TØMRERMESTER LYCHE & SIMONSEN AS has its business address in Oslo.

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.