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

HEMSEDAL TØMRERBYGG AS

Org. no. 927135361 Limited company (AS) Hemsedal Incorporated 2021 Active
Revenue 2025 NOK 715,000
Operating profit NOK 33,000
Equity NOK 332,000
Incorporated 2021
Share capital NOK 30,000

HEMSEDAL TØMRERBYGG AS is registered as a limited company in Hemsedal, Buskerud with organisation number 927135361. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tømrer og snekkervirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 715,000 in revenue and NOK 33,000 in operating profit.

Key figures · 2025

Revenue
NOK 715,000
▼ −48 %
Operating profit
NOK 33,000
▼ −85 %
Equity
NOK 332,000
▲ +7 %
Est. value
NOK 371,000

Financial health · 2025

Liquidity
3.39
Very good
Current assets ÷ current liabilities
Profitability
6.8%
Satisfactory
Return on total assets
Solidity
80.2%
Very good
Equity as a share of total capital

Who owns HEMSEDAL TØMRERBYGG AS?

HEMSEDAL TØMRERBYGG AS
NOK 715,000 rev. · NOK 33,000 profit

HEMSEDAL TØMRERBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEMSEDAL TØMRERBYGG AS

Who owns HEMSEDAL TØMRERBYGG AS?

Sandokan Nosha is the largest registered owner, with 100.0%.

What is the revenue of HEMSEDAL TØMRERBYGG AS?

HEMSEDAL TØMRERBYGG AS had revenue of NOK 715,000 in 2025.

Who is the general manager of HEMSEDAL TØMRERBYGG AS?

Sandokan Nosha is registered as general manager of HEMSEDAL TØMRERBYGG AS.

Where is HEMSEDAL TØMRERBYGG AS based?

HEMSEDAL TØMRERBYGG AS has its business address in Hemsedal.

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.