biztrac. BETA
COMPANY REGISTER PROFILE
915762662 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SKE INVEST AS

Org. no. 915762662 Limited company (AS) Porsgrunn Incorporated 2015 Active
Operating profit NOK −14,000
Equity NOK 23.5m
Incorporated 2015
Share capital NOK 30,000

Signals

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

SKE INVEST AS is registered as a limited company in Porsgrunn, Telemark with organisation number 915762662. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og eiendom, utleie og oppføring av bygg samt hva herved står i forbindelse. Salg av konsulenttjenester innen automasjon og andre tjenester/produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −14,000
▼ −10 %
Equity
NOK 23.5m
▲ +648 %
Est. value
NOK 92.3m

Financial health · 2025

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

Who owns SKE INVEST AS?

SKE INVEST AS
· NOK −14,000 profit

SKE INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKE INVEST AS own?

SKE INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKE INVEST AS

Who owns SKE INVEST AS?

Sondre Keim is the largest registered owner, with 100.0%.

Where is SKE INVEST AS based?

SKE INVEST AS has its business address in Porsgrunn.

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

Report a problem

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