BIZTRAC BETA
Buying and selling of own real estate

SLA EIENDOM AS

Org. no. 984831633 Limited company (AS) Bodø Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 711,000
Equity NOK 4.5m
Incorporated 2002
Employees 6
Share capital NOK 200,000

SLA EIENDOM AS is registered as a limited company in Bodø, Nordland with organisation number 984831633. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2002 and has 6 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Servicenæring og kjøp/salg innenfor eiendomsbransjen, herunder også deltakelse i annen næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 711,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK 711,000
Equity
NOK 4.5m
Est. value
NOK 4.9m

Financial health · 2025

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

Who owns SLA EIENDOM AS?

SIGURD PETER RYDLAND
SLA EIENDOM AS
NOK 4.5m rev. · NOK 711,000 profit

SLA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SLA EIENDOM AS own?

SLA EIENDOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SLA EIENDOM AS

Who owns SLA EIENDOM AS?

SIGURD PETER RYDLAND is the largest registered owner, with 100.0%.

What is the revenue of SLA EIENDOM AS?

SLA EIENDOM AS had revenue of NOK 4.5m in 2025.

Who is the general manager of SLA EIENDOM AS?

Atle Olsen Rydland is registered as general manager of SLA EIENDOM AS.

Where is SLA EIENDOM AS based?

SLA EIENDOM AS has its business address in Bodø.

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.