BIZTRAC BETA
Construction of residential and non-residential buildings

STILBYGG KONGSBERG AS

Org. no. 981634632 Limited company (AS) Kongsberg Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 16.8m
Operating profit NOK 1.1m
Equity NOK 2.6m
Incorporated 2000
Employees 9
Share capital NOK 100,000

STILBYGG KONGSBERG AS is registered as a limited company in Kongsberg, Buskerud with organisation number 981634632. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2000 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Oppføring av boliger og andre bygningskonstruksjoner og det som naturlig hører sammen med slik virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 16.8m
Operating profit
NOK 1.1m
Equity
NOK 2.6m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns STILBYGG KONGSBERG AS?

TOR EGIL LANDE
STILBYGG KONGSBERG AS
NOK 16.8m rev. · NOK 1.1m profit

STILBYGG KONGSBERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STILBYGG KONGSBERG AS

Who owns STILBYGG KONGSBERG AS?

TOR EGIL LANDE is the largest registered owner, with 100.0%.

What is the revenue of STILBYGG KONGSBERG AS?

STILBYGG KONGSBERG AS had revenue of NOK 16.8m in 2025.

Who is the general manager of STILBYGG KONGSBERG AS?

Tor Egil Lande is registered as general manager of STILBYGG KONGSBERG AS.

Where is STILBYGG KONGSBERG AS based?

STILBYGG KONGSBERG AS has its business address in Skollenborg.

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.