BIZTRAC BETA
Rental and operating of own or leased real estate

VS-BOLIG AS

Org. no. 921792883 Limited company (AS) Kristiansand Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 894,000
Operating profit NOK 323,000
Equity NOK 428,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-06-24 Adresseendring registrert 2026-06-24.

VS-BOLIG AS is registered as a limited company in Kristiansand, Agder with organisation number 921792883. 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 30,000, divided into 30 shares. The company's stated purpose is: “Eie og drive fast eiendom, samt hva dermed står i forbindelse. Herunder deltakelse i andre selskaper med tilsvarende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 894,000 in revenue and NOK 323,000 in operating profit.

Key figures · 2025

Revenue
NOK 894,000
Operating profit
NOK 323,000
Equity
NOK 428,000
Est. value
NOK 846,000

Financial health · 2025

Liquidity
3.46
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.3%
Weak
Equity as a share of total capital

Who owns VS-BOLIG AS?

NYE MJI MØRK & JACOBSEN INVEST AS
VS-BOLIG AS
NOK 894,000 rev. · NOK 323,000 profit

VS-BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VS-BOLIG AS

Who owns VS-BOLIG AS?

NYE MJI MØRK & JACOBSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of VS-BOLIG AS?

VS-BOLIG AS had revenue of NOK 894,000 in 2025.

Where is VS-BOLIG AS based?

VS-BOLIG AS has its business address in Kristiansand S.

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.