BIZTRAC BETA
Rental and operating of own or leased real estate

SL EIENDOM OG INVEST AS

Org. no. 891860862 Limited company (AS) Rakkestad Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 620,000
Equity NOK 6.9m
Incorporated 2007
Share capital NOK 100,000

SL EIENDOM OG INVEST AS is registered as a limited company in Rakkestad, Østfold with organisation number 891860862. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 25 shares. The company's stated purpose is: “Eie, forvalte, kjøpe og selge eiendom, varige driftsmidler, andeler/aksjer i andre selskaper og virksomhet som har sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9m in revenue and NOK 620,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 620,000
Equity
NOK 6.9m
Est. value
NOK 6.0m

Financial health · 2025

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

Who owns SL EIENDOM OG INVEST AS?

STEINAR LEVERNES
SL EIENDOM OG INVEST AS
NOK 1.9m rev. · NOK 620,000 profit

SL EIENDOM OG INVEST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SL EIENDOM OG INVEST AS

Who owns SL EIENDOM OG INVEST AS?

STEINAR LEVERNES is the largest registered owner, with 52.0%.

What is the revenue of SL EIENDOM OG INVEST AS?

SL EIENDOM OG INVEST AS had revenue of NOK 1.9m in 2025.

Who is the general manager of SL EIENDOM OG INVEST AS?

Steinar Levernes is registered as general manager of SL EIENDOM OG INVEST AS.

Where is SL EIENDOM OG INVEST AS based?

SL EIENDOM OG INVEST AS has its business address in Rakkestad.

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.