BIZTRAC BETA
Rental and operating of own or leased real estate

S 2 SANDEFJORD AS

Org. no. 921894244 Limited company (AS) Sandefjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 293,000
Operating profit NOK 210,000
Equity NOK 501,000
Incorporated 2018
Share capital NOK 319,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 2 SANDEFJORD AS is registered as a limited company in Sandefjord, Vestfold with organisation number 921894244. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 319,000, divided into 319245 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom og hva dermed står i naturlig forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 293,000 in revenue and NOK 210,000 in operating profit.

Key figures · 2024

Revenue
NOK 293,000
Operating profit
NOK 210,000
Equity
NOK 501,000
Est. value
NOK 777,000

Financial health · 2024

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

Who owns S 2 SANDEFJORD AS?

LINHOLM AS
S 2 SANDEFJORD AS
NOK 293,000 rev. · NOK 210,000 profit

S 2 SANDEFJORD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

S 2 SANDEFJORD AS er morselskap for 41 datterselskaper:

Frequently asked questions about S 2 SANDEFJORD AS

Who owns S 2 SANDEFJORD AS?

LINHOLM AS is the largest registered owner, with 100.0%.

What is the revenue of S 2 SANDEFJORD AS?

S 2 SANDEFJORD AS had revenue of NOK 293,000 in 2024.

Where is S 2 SANDEFJORD AS based?

S 2 SANDEFJORD AS has its business address in Sandefjord.

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.