BIZTRAC BETA
Rental and operating of own or leased real estate

RØRHUS AS

Org. no. 943561001 Limited company (AS) Lillesand Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 637,000
Equity NOK 2.1m
Incorporated 1987
Share capital NOK 37,000

Signals

1 flags
  • Nylig endring 2026-02-20 Adresseendring registrert 2026-02-20.

RØRHUS AS is registered as a limited company in Lillesand, Agder with organisation number 943561001. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 37,000, divided into 100 shares. The company's stated purpose is: “Utvikle, eie og drifte fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 637,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 637,000
Equity
NOK 2.1m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns RØRHUS AS?

LMJ HOLDING AS
RØRHUS AS
NOK 1.1m rev. · NOK 637,000 profit

RØRHUS AS has 2 registered shareholders:

All shareholders and roles →

Which companies does RØRHUS AS own?

RØRHUS AS holds a stake in 1 company:

See the full ownership structure →

Group structure

RØRHUS AS er morselskap for 4 datterselskaper:

Frequently asked questions about RØRHUS AS

Who owns RØRHUS AS?

LMJ HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of RØRHUS AS?

RØRHUS AS had revenue of NOK 1.1m in 2025.

Who is the general manager of RØRHUS AS?

Lars Morten Johannessen is registered as general manager of RØRHUS AS.

Where is RØRHUS AS based?

RØRHUS AS has its business address in Lillesand.

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.