biztrac. BETA
COMPANY REGISTER PROFILE
922047944 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

TRANBY TØMRERNE AS

Org. no. 922047944 Limited company (AS) Lier Incorporated 2018 Active
Revenue 2025 NOK 4.8m
Operating profit NOK 37,000
Equity NOK 215,000
Incorporated 2018
Employees 5
Share capital NOK 30,000

TRANBY TØMRERNE AS is registered as a limited company in Lier, Buskerud with organisation number 922047944. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Håndverkertjenester. Dette omfatter nybygg, renovering, serviceoppdrag samt salg av relevant materiell til nevnte oppgave.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 37,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
▲ +10 %
Operating profit
NOK 37,000
▼ −72 %
Equity
NOK 215,000
▲ +6 %
Est. value
NOK 274,000

Financial health · 2025

Liquidity
1.40
Satisfactory
Current assets ÷ current liabilities
Profitability
3.6%
Weak
Return on total assets
Solidity
23.4%
Good
Equity as a share of total capital

Who owns TRANBY TØMRERNE AS?

TRANBY TØMRERNE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRANBY TØMRERNE AS

Who owns TRANBY TØMRERNE AS?

Aleksander Nomme is the largest registered owner, with 49.0%.

What is the revenue of TRANBY TØMRERNE AS?

TRANBY TØMRERNE AS had revenue of NOK 4.8m in 2025.

Who is the general manager of TRANBY TØMRERNE AS?

Aleksander Nomme is registered as general manager of TRANBY TØMRERNE AS.

Where is TRANBY TØMRERNE AS based?

TRANBY TØMRERNE AS has its business address in Tranby.

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.