BIZTRAC BETA
Construction of residential and non-residential buildings

RIV OG RØSK AS

Org. no. 930463310 Limited company (AS) Lillestrøm Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 8,000
Operating profit NOK −39,000
Equity NOK 53,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

RIV OG RØSK AS is registered as a limited company in Lillestrøm, Akershus with organisation number 930463310. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Bygningsarbeidsarbeid og salg av varer og tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 8,000 in revenue and NOK −39,000 in operating profit.

Key figures · 2024

Revenue
NOK 8,000
Operating profit
NOK −39,000
Equity
NOK 53,000
Est. value
NOK 25,000

Financial health · 2024

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

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

Who owns RIV OG RØSK AS?

FYRHUSET HOLDING AS
RIV OG RØSK AS
NOK 8,000 rev. · NOK −39,000 profit

RIV OG RØSK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RIV OG RØSK AS

Who owns RIV OG RØSK AS?

FYRHUSET HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RIV OG RØSK AS?

RIV OG RØSK AS had revenue of NOK 8,000 in 2024.

Who is the general manager of RIV OG RØSK AS?

Jo Bendik Mangal Olsen is registered as general manager of RIV OG RØSK AS.

Where is RIV OG RØSK AS based?

RIV OG RØSK AS has its business address in Skedsmokorset.

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.