BIZTRAC BETA
Business and other management consultancy activities

SIVILINGENIØR JAN RONESS AS

Org. no. 858169852 Limited company (AS) Lindesnes Incorporated 1990 Active
Ownership graph ↗
Operating profit NOK −921,000
Equity NOK 4.6m
Incorporated 1990
Share capital NOK 100,000

Signals

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

SIVILINGENIØR JAN RONESS AS is registered as a limited company in Lindesnes, Agder with organisation number 858169852. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Konsulentvirksomhet, handel inkludert handel med valuta, samt alt hva dermed står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”.

Key figures · 2024

Operating profit
NOK −921,000
Equity
NOK 4.6m
Est. value
NOK 7.5m

Financial health · 2024

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

Who owns SIVILINGENIØR JAN RONESS AS?

JAN MARGIDION RONESS
SIVILINGENIØR JAN RONESS AS
· NOK −921,000 profit

SIVILINGENIØR JAN RONESS AS has 3 registered shareholders:

All shareholders and roles →

Group structure

SIVILINGENIØR JAN RONESS AS er morselskap for 1 datterselskap:

Frequently asked questions about SIVILINGENIØR JAN RONESS AS

Who owns SIVILINGENIØR JAN RONESS AS?

JAN MARGIDION RONESS is the largest registered owner, with 64.0%.

Who is the general manager of SIVILINGENIØR JAN RONESS AS?

Jan Margidion Roness is registered as general manager of SIVILINGENIØR JAN RONESS AS.

Where is SIVILINGENIØR JAN RONESS AS based?

SIVILINGENIØR JAN RONESS AS has its business address in Mandal.

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.