BIZTRAC BETA
Rental and operating of own or leased real estate

VESTRE ANDEBU VEI 493 AS

Org. no. 933486222 Limited company (AS) Sandefjord Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 400,000
Operating profit NOK 316,000
Equity NOK 323,000
Incorporated 2024
Share capital NOK 52,000

Signals

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

VESTRE ANDEBU VEI 493 AS is registered as a limited company in Sandefjord, Vestfold with organisation number 933486222. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 52,000, divided into 52 shares. The company's stated purpose is: “Eie og forvalte fast eiendom samt det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 400,000 in revenue and NOK 316,000 in operating profit.

Key figures · 2024

Revenue
NOK 400,000
Operating profit
NOK 316,000
Equity
NOK 323,000
Est. value
NOK 769,000

Financial health · 2024

Liquidity
5.26
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.7%
Satisfactory
Equity as a share of total capital

Who owns VESTRE ANDEBU VEI 493 AS?

JØRN SKJELBRED AS
VESTRE ANDEBU VEI 493 AS
NOK 400,000 rev. · NOK 316,000 profit

VESTRE ANDEBU VEI 493 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTRE ANDEBU VEI 493 AS

Who owns VESTRE ANDEBU VEI 493 AS?

JØRN SKJELBRED AS is the largest registered owner, with 100.0%.

What is the revenue of VESTRE ANDEBU VEI 493 AS?

VESTRE ANDEBU VEI 493 AS had revenue of NOK 400,000 in 2024.

Where is VESTRE ANDEBU VEI 493 AS based?

VESTRE ANDEBU VEI 493 AS has its business address in Andebu.

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.