BIZTRAC BETA
Site preparation

RØSHOLT ENTREPRENØR AS

Org. no. 913522168 Limited company (AS) Larvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 10.5m
Operating profit NOK 91,000
Equity NOK 7.2m
Incorporated 2014
Share capital NOK 60,000

RØSHOLT ENTREPRENØR AS is registered as a limited company in Larvik, Vestfold with organisation number 913522168. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 60,000, divided into 30 shares. The company's stated purpose is: “Entreprenørvirksomhet i anleggsbransjen og investering i eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.5m in revenue and NOK 91,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.5m
Operating profit
NOK 91,000
Equity
NOK 7.2m
Est. value
NOK 3.4m

Financial health · 2024

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

Who owns RØSHOLT ENTREPRENØR AS?

RØSHOLT ENTREPRENØR AS
RØSHOLT ENTREPRENØR AS
NOK 10.5m rev. · NOK 91,000 profit

RØSHOLT ENTREPRENØR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does RØSHOLT ENTREPRENØR AS own?

RØSHOLT ENTREPRENØR AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about RØSHOLT ENTREPRENØR AS

Who owns RØSHOLT ENTREPRENØR AS?

RØSHOLT ENTREPRENØR AS is the largest registered owner, with 50.0%.

What is the revenue of RØSHOLT ENTREPRENØR AS?

RØSHOLT ENTREPRENØR AS had revenue of NOK 10.5m in 2024.

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

Sven-Gunnar Røsholt is registered as general manager of RØSHOLT ENTREPRENØR AS.

Where is RØSHOLT ENTREPRENØR AS based?

RØSHOLT ENTREPRENØR AS has its business address in Svarstad.

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.