BIZTRAC BETA
Construction of residential and non-residential buildings

SILKOSET BYGG AS

Org. no. 983928447 Limited company (AS) Elverum Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 7.9m
Operating profit NOK 873,000
Equity NOK 979,000
Incorporated 2001
Employees 5
Share capital NOK 100,000

SILKOSET BYGG AS is registered as a limited company in Elverum, Innlandet with organisation number 983928447. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2001 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Omsette håndverkstjenester i forbindelse med nybygg og tilbygg samt rehabilitering av bygg og salg av byggevarer som naturlig faller inn under denne næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK 873,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.9m
Operating profit
NOK 873,000
Equity
NOK 979,000
Est. value
NOK 3.1m

Financial health · 2025

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

Who owns SILKOSET BYGG AS?

ROGER SILKOSET
SILKOSET BYGG AS
NOK 7.9m rev. · NOK 873,000 profit

SILKOSET BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SILKOSET BYGG AS

Who owns SILKOSET BYGG AS?

ROGER SILKOSET is the largest registered owner, with 100.0%.

What is the revenue of SILKOSET BYGG AS?

SILKOSET BYGG AS had revenue of NOK 7.9m in 2025.

Who is the general manager of SILKOSET BYGG AS?

Roger Silkoset is registered as general manager of SILKOSET BYGG AS.

Where is SILKOSET BYGG AS based?

SILKOSET BYGG AS has its business address in Elverum.

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.