BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

RUDLENDE EIENDOM AS

Org. no. 988971634 Limited company (AS) Farsund Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 384,000
Equity NOK 16.0m
Incorporated 2005
Share capital NOK 1.0m

RUDLENDE EIENDOM AS is registered as a limited company in Farsund, Agder with organisation number 988971634. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Anskaffelse, utleie og drift av eiendommer samt alt hva derved står i forbindelse, herunder gjennom aksjetegning eller på annen måte å delta i andre selskaper eller foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 384,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 384,000
Equity
NOK 16.0m
Est. value
NOK 9.8m

Financial health · 2025

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

Who owns RUDLENDE EIENDOM AS?

ROJ INVEST AS
RUDLENDE EIENDOM AS
NOK 1.2m rev. · NOK 384,000 profit

RUDLENDE EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about RUDLENDE EIENDOM AS

Who owns RUDLENDE EIENDOM AS?

ROJ INVEST AS is the largest registered owner, with 64.8%.

What is the revenue of RUDLENDE EIENDOM AS?

RUDLENDE EIENDOM AS had revenue of NOK 1.2m in 2025.

Who is the general manager of RUDLENDE EIENDOM AS?

Odd Bjørn Rudlende is registered as general manager of RUDLENDE EIENDOM AS.

Where is RUDLENDE EIENDOM AS based?

RUDLENDE EIENDOM AS has its business address in Vanse.

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.