BIZTRAC BETA
COMPANY REGISTER PROFILE
990649979 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Plumbing installation

RISØR RØR AS

Org. no. 990649979 Limited company (AS) Risør Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −7,000
Equity NOK −462,000
Incorporated 2006
Share capital NOK 456,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−462k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−7k kr).

RISØR RØR AS is registered as a limited company in Risør, Agder with organisation number 990649979. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2006. Registered share capital is NOK 456,000, divided into 4001 shares. The company's stated purpose is: “Rørleggerservice, samt salg av VVS-varer.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK −462,000

Financial health · 2024

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4787.8%
Weak
Equity as a share of total capital

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

Who owns RISØR RØR AS?

EINAR ANDRE LANES
RISØR RØR AS
NOK 0 rev. · NOK −7,000 profit

RISØR RØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RISØR RØR AS

Who owns RISØR RØR AS?

EINAR ANDRE LANES is the largest registered owner, with 100.0%.

What is the revenue of RISØR RØR AS?

RISØR RØR AS had revenue of NOK 0 in 2024.

Who is the general manager of RISØR RØR AS?

Einar Andre Lanes is registered as general manager of RISØR RØR AS.

Where is RISØR RØR AS based?

RISØR RØR AS has its business address in Risør.

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.