BIZTRAC BETA
COMPANY REGISTER PROFILE
835554112 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 25.08.2026
Uoppgitt

SLR INVESTERING AS

Org. no. 835554112 Limited company (AS) Kinn Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 344,000
Incorporated 2025
Share capital NOK 350,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−7k kr).

SLR INVESTERING AS is registered as a limited company in Kinn, Vestland with organisation number 835554112. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 350,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andre finansielle instrumenter, samt annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 344,000
Est. value
NOK 404,000

Financial health · 2025

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

Who owns SLR INVESTERING AS?

SLR INVESTERING AS
NOK 0 rev. · NOK −7,000 profit

SLR INVESTERING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SLR INVESTERING AS own?

SLR INVESTERING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SLR INVESTERING AS

Who owns SLR INVESTERING AS?

STINE LIABØ ROGNSØ is the largest registered owner, with 100.0%.

What is the revenue of SLR INVESTERING AS?

SLR INVESTERING AS had revenue of NOK 0 in 2025.

Where is SLR INVESTERING AS based?

SLR INVESTERING AS has its business address in Florø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.