biztrac. BETA
COMPANY REGISTER PROFILE
915682839 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

SOLVIG ENTREPRENØR AS

Org. no. 915682839 Limited company (AS) Karmøy Incorporated 2015 Active
Revenue 2025 NOK 1.4m
Operating profit NOK 94,000
Equity NOK 16,000
Incorporated 2015
Share capital NOK 30,000

SOLVIG ENTREPRENØR AS is registered as a limited company in Karmøy, Rogaland with organisation number 915682839. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet, herunder graving, steinlegging, transport og beslektet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 94,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
▲ +11 %
Operating profit
NOK 94,000
▼ −35 %
Equity
NOK 16,000
▲ +125 %
Est. value
NOK 337,000

Financial health · 2025

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
34.3%
Very good
Return on total assets
Solidity
4.7%
Weak
Equity as a share of total capital

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

Who owns SOLVIG ENTREPRENØR AS?

SOLVIG ENTREPRENØR AS
NOK 1.4m rev. · NOK 94,000 profit

SOLVIG ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLVIG ENTREPRENØR AS

Who owns SOLVIG ENTREPRENØR AS?

Rita Landa is the largest registered owner, with 100.0%.

What is the revenue of SOLVIG ENTREPRENØR AS?

SOLVIG ENTREPRENØR AS had revenue of NOK 1.4m in 2025.

Who is the general manager of SOLVIG ENTREPRENØR AS?

Knut Andre Solvig is registered as general manager of SOLVIG ENTREPRENØR AS.

Where is SOLVIG ENTREPRENØR AS based?

SOLVIG ENTREPRENØR AS has its business address in Kopervik.

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.