BIZTRAC BETA
Construction of residential and non-residential buildings

TRADISJONELT BYGG HÅNDVERK AS

Org. no. 918070206 Limited company (AS) Oslo Incorporated 1978 Active
Ownership graph ↗
Revenue 2025 NOK 5.6m
Operating profit NOK 201,000
Equity NOK 2.7m
Incorporated 1978
Share capital NOK 100,000

TRADISJONELT BYGG HÅNDVERK AS is registered as a limited company in Oslo, Oslo with organisation number 918070206. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1978. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Tømmermesterforretning og dermed sammenhengende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.6m in revenue and NOK 201,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.6m
Operating profit
NOK 201,000
Equity
NOK 2.7m
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns TRADISJONELT BYGG HÅNDVERK AS?

JONNY ANDERSEN
TRADISJONELT BYGG HÅNDVERK AS
NOK 5.6m rev. · NOK 201,000 profit

TRADISJONELT BYGG HÅNDVERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRADISJONELT BYGG HÅNDVERK AS

Who owns TRADISJONELT BYGG HÅNDVERK AS?

JONNY ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of TRADISJONELT BYGG HÅNDVERK AS?

TRADISJONELT BYGG HÅNDVERK AS had revenue of NOK 5.6m in 2025.

Who is the general manager of TRADISJONELT BYGG HÅNDVERK AS?

Pål Halvorsen is registered as general manager of TRADISJONELT BYGG HÅNDVERK AS.

Where is TRADISJONELT BYGG HÅNDVERK AS based?

TRADISJONELT BYGG HÅNDVERK 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.