biztrac. BETA
COMPANY REGISTER PROFILE
923626387 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SK PROPERTY INVEST AS

Org. no. 923626387 Limited company (AS) Skien Incorporated 2019 Active
Operating profit NOK −99,000
Equity NOK −1.4m
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,4 mill kr).

SK PROPERTY INVEST AS is registered as a limited company in Skien, Telemark with organisation number 923626387. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Kjøp/salg og utleie av eiendom, samt utføre snekkertjenester, og annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2024

Operating profit
NOK −99,000
▲ +46 %
Equity
NOK −1.4m
▼ −51 %

Financial health · 2024

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
-2.8%
Not satisfactory
Return on total assets
Solidity
-37.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SK PROPERTY INVEST AS?

SK PROPERTY INVEST AS
· NOK −99,000 profit

SK PROPERTY INVEST AS has 2 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2023.

All shareholders and roles →

Frequently asked questions about SK PROPERTY INVEST AS

Who owns SK PROPERTY INVEST AS?

Leon Sejdiu is the largest registered owner, with 50.0%.

Who is the general manager of SK PROPERTY INVEST AS?

Leon Sejdiu is registered as general manager of SK PROPERTY INVEST AS.

Where is SK PROPERTY INVEST AS based?

SK PROPERTY INVEST AS has its business address in Skien.

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.