BIZTRAC BETA
Silviculture and other forestry activities

RØRVIK TAUBANEDRIFT AS

Org. no. 979451369 Limited company (AS) Sandnes Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 8.7m
Operating profit NOK −276,000
Equity NOK 622,000
Incorporated 1997
Share capital NOK 100,000

Signals

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

RØRVIK TAUBANEDRIFT AS is registered as a limited company in Sandnes, Rogaland with organisation number 979451369. The business is classified under silviculture and other forestry activities (NACE 02.100). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Skogbruk og tjenester tilknyttet skogbruk.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.7m in revenue and NOK −276,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.7m
Operating profit
NOK −276,000
Equity
NOK 622,000
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns RØRVIK TAUBANEDRIFT AS?

GRETHE MARIE RØRVIK
RØRVIK TAUBANEDRIFT AS
NOK 8.7m rev. · NOK −276,000 profit

RØRVIK TAUBANEDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RØRVIK TAUBANEDRIFT AS

Who owns RØRVIK TAUBANEDRIFT AS?

GRETHE MARIE RØRVIK is the largest registered owner, with 100.0%.

What is the revenue of RØRVIK TAUBANEDRIFT AS?

RØRVIK TAUBANEDRIFT AS had revenue of NOK 8.7m in 2024.

Who is the general manager of RØRVIK TAUBANEDRIFT AS?

Grethe Marie Rørvik is registered as general manager of RØRVIK TAUBANEDRIFT AS.

Where is RØRVIK TAUBANEDRIFT AS based?

RØRVIK TAUBANEDRIFT AS has its business address in Hommersåk.

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.