BIZTRAC BETA
Rental and operating of own or leased real estate

S&K EIENDOM AS

Org. no. 998942152 Limited company (AS) Sortland Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 204,000
Equity NOK 1.7m
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

S&K EIENDOM AS is registered as a limited company in Sortland, Nordland with organisation number 998942152. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg, utvikling og forvaltning av fast eiendom samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 204,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 204,000
Equity
NOK 1.7m
Est. value
NOK 1.5m

Financial health · 2025

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

Who owns S&K EIENDOM AS?

SAK HOLDING AS
S&K EIENDOM AS
NOK 1.0m rev. · NOK 204,000 profit

S&K EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about S&K EIENDOM AS

Who owns S&K EIENDOM AS?

SAK HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of S&K EIENDOM AS?

S&K EIENDOM AS had revenue of NOK 1.0m in 2025.

Who is the general manager of S&K EIENDOM AS?

Stig Are Karlsen is registered as general manager of S&K EIENDOM AS.

Where is S&K EIENDOM AS based?

S&K EIENDOM AS has its business address in Sortland.

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.