BIZTRAC BETA
Site preparation

RONDANE ENTREPRENØR AS

Org. no. 988850306 Limited company (AS) Sør-Fron Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK −162,000
Equity NOK 635,000
Incorporated 2005
Share capital NOK 140,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−162k kr).

RONDANE ENTREPRENØR AS is registered as a limited company in Sør-Fron, Innlandet with organisation number 988850306. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005. Registered share capital is NOK 140,000, divided into 1270 shares. The company's stated purpose is: “Drive entrepenørvirksomhet, samt og investere direkte eller indirekte i andre foretagender av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK −162,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK −162,000
Equity
NOK 635,000
Est. value
NOK 651,000

Financial health · 2024

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.8%
Satisfactory
Equity as a share of total capital

Who owns RONDANE ENTREPRENØR AS?

SINDRE SPIDSBERG
RONDANE ENTREPRENØR AS
NOK 3.5m rev. · NOK −162,000 profit

RONDANE ENTREPRENØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RONDANE ENTREPRENØR AS

Who owns RONDANE ENTREPRENØR AS?

SINDRE SPIDSBERG is the largest registered owner, with 100.0%.

What is the revenue of RONDANE ENTREPRENØR AS?

RONDANE ENTREPRENØR AS had revenue of NOK 3.5m in 2024.

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

Sindre Spidsberg is registered as general manager of RONDANE ENTREPRENØR AS.

Where is RONDANE ENTREPRENØR AS based?

RONDANE ENTREPRENØR AS has its business address in Sør-Fron.

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.