BIZTRAC BETA
Buying and selling of own real estate

NYVOLL BOLIG AS

Org. no. 925347531 Limited company (AS) Tønsberg Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 2.7m
Equity NOK 8.3m
Incorporated 2020
Share capital NOK 30,000

Signals

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

NYVOLL BOLIG AS is registered as a limited company in Tønsberg, Vestfold with organisation number 925347531. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg, utleie, utvikling av fast eiendom, samt hva som herved står i forbindelse, herunder deltakelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
Operating profit
NOK 2.7m
Equity
NOK 8.3m
Est. value
NOK 13.0m

Financial health · 2024

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

Who owns NYVOLL BOLIG AS?

JON INVEST AS
NYVOLL BOLIG AS
NOK 6.0m rev. · NOK 2.7m profit

NYVOLL BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYVOLL BOLIG AS

Who owns NYVOLL BOLIG AS?

JON INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of NYVOLL BOLIG AS?

NYVOLL BOLIG AS had revenue of NOK 6.0m in 2025.

Who is the general manager of NYVOLL BOLIG AS?

Jon Oskar Nyvoll is registered as general manager of NYVOLL BOLIG AS.

Where is NYVOLL BOLIG AS based?

NYVOLL BOLIG AS has its business address in Revetal.

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.