BIZTRAC BETA
Other specialised construction activities n.e.c.

SELVIK BYGG OG INDUSTRI AS

Org. no. 924118563 Limited company (AS) Sauda Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 58,000
Equity NOK 89,000
Incorporated 2019
Share capital NOK 30,000

SELVIK BYGG OG INDUSTRI AS is registered as a limited company in Sauda, Rogaland with organisation number 924118563. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Anleggsarbeid, reparasjon av maskiner og utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 58,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 58,000
Equity
NOK 89,000
Est. value
NOK 189,000

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SELVIK BYGG OG INDUSTRI AS?

NIKOLAI SELVIK
SELVIK BYGG OG INDUSTRI AS
NOK 2.1m rev. · NOK 58,000 profit

SELVIK BYGG OG INDUSTRI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SELVIK BYGG OG INDUSTRI AS

Who owns SELVIK BYGG OG INDUSTRI AS?

NIKOLAI SELVIK is the largest registered owner, with 100.0%.

What is the revenue of SELVIK BYGG OG INDUSTRI AS?

SELVIK BYGG OG INDUSTRI AS had revenue of NOK 2.1m in 2025.

Who is the general manager of SELVIK BYGG OG INDUSTRI AS?

Nikolai Selvik is registered as general manager of SELVIK BYGG OG INDUSTRI AS.

Where is SELVIK BYGG OG INDUSTRI AS based?

SELVIK BYGG OG INDUSTRI AS has its business address in Saudasjøen.

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.