BIZTRAC BETA
Civil engineering activities

SOLRING ANLEGGSTENESTER AS

Org. no. 935067340 Limited company (AS) Vinje Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 828,000
Operating profit NOK 188,000
Equity NOK 172,000
Incorporated 2025
Share capital NOK 30,000

SOLRING ANLEGGSTENESTER AS is registered as a limited company in Vinje, Telemark with organisation number 935067340. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Alt innenfor bygg og anlegg, og det som naturlig høyrer til. Konsulentvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 828,000 in revenue and NOK 188,000 in operating profit.

Key figures · 2025

Revenue
NOK 828,000
Operating profit
NOK 188,000
Equity
NOK 172,000
Est. value
NOK 826,000

Financial health · 2025

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

Who owns SOLRING ANLEGGSTENESTER AS?

SOLVEIG NORDHEIM RINGHUS
SOLRING ANLEGGSTENESTER AS
NOK 828,000 rev. · NOK 188,000 profit

SOLRING ANLEGGSTENESTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOLRING ANLEGGSTENESTER AS

Who owns SOLRING ANLEGGSTENESTER AS?

SOLVEIG NORDHEIM RINGHUS is the largest registered owner, with 50.0%.

What is the revenue of SOLRING ANLEGGSTENESTER AS?

SOLRING ANLEGGSTENESTER AS had revenue of NOK 828,000 in 2025.

Who is the general manager of SOLRING ANLEGGSTENESTER AS?

Solveig Nordheim Ringhus is registered as general manager of SOLRING ANLEGGSTENESTER AS.

Where is SOLRING ANLEGGSTENESTER AS based?

SOLRING ANLEGGSTENESTER AS has its business address in Vinje.

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.