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

SV22H AS

Org. no. 888815252 Limited company (AS) Holmestrand Incorporated 2005 Active
Revenue 2024 NOK 630,000
Operating profit NOK 277,000
Equity NOK 248,000
Incorporated 2005
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.

SV22H AS is registered as a limited company in Holmestrand, Vestfold with organisation number 888815252. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 630,000 in revenue and NOK 277,000 in operating profit.

Former names: REKKEVIK EIENDOM AS, NANSET EIENDOM AS, FRA BOLIG TIL HJEM AS, SENTRUMSVEIEN 22 AS

Key figures · 2024

Revenue
NOK 630,000
▲ +293 %
Operating profit
NOK 277,000
▲ +522 %
Equity
NOK 248,000
▼ −24 %
Est. value
NOK 455,000

Financial health · 2024

Liquidity
0.08
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
4.5%
Weak
Equity as a share of total capital

Who owns SV22H AS?

SV22H AS
NOK 630,000 rev. · NOK 277,000 profit

SV22H AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SV22H AS

Who owns SV22H AS?

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

What is the revenue of SV22H AS?

SV22H AS had revenue of NOK 630,000 in 2024.

Where is SV22H AS based?

SV22H AS has its business address in Holmestrand.

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.