biztrac. BETA
COMPANY REGISTER PROFILE
976593715 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Wholesale of wood, construction materials and sanitary equipment

SELBU BYGGVARE AS

Org. no. 976593715 Limited company (AS) Selbu Incorporated 1996 Active
Revenue 2025 NOK 74.0m
Operating profit NOK 756,000
Equity NOK 4.8m
Incorporated 1996
Employees 22
Share capital NOK 200,000

SELBU BYGGVARE AS is registered as a limited company in Selbu, Trøndelag with organisation number 976593715. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 1996 and has 22 registered employees. Registered share capital is NOK 200,000. The company's stated purpose is: “Byggshopvirksomhet, økonomisk virksomhet av enhver art, samt delta i slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 74.0m in revenue and NOK 756,000 in operating profit.

Key figures · 2025

Revenue
NOK 74.0m
▲ +14 %
Operating profit
NOK 756,000
▲ +127 %
Equity
NOK 4.8m
▼ −16 %
Est. value
NOK 16.1m

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
3.0%
Weak
Return on total assets
Solidity
20.9%
Good
Equity as a share of total capital

Who owns SELBU BYGGVARE AS?

SELBU BYGGVARE AS
NOK 74.0m rev. · NOK 756,000 profit

SELBU BYGGVARE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SELBU BYGGVARE AS

Who owns SELBU BYGGVARE AS?

SELBU GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of SELBU BYGGVARE AS?

SELBU BYGGVARE AS had revenue of NOK 74.0m in 2025.

Who is the general manager of SELBU BYGGVARE AS?

Kim André Eidem is registered as general manager of SELBU BYGGVARE AS.

Where is SELBU BYGGVARE AS based?

SELBU BYGGVARE AS has its business address in Selbu.

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.