BIZTRAC BETA
Buying and selling of own real estate

KULLERØDSVINGEN AS

Org. no. 829669382 Limited company (AS) Tønsberg Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 26.7m
Operating profit NOK 2.1m
Equity NOK 2.1m
Incorporated 2022
Share capital NOK 500,000

Signals

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

KULLERØDSVINGEN AS is registered as a limited company in Tønsberg, Vestfold with organisation number 829669382. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2022. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Kjøp, salg og utvikling av fast eiendom samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.7m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 26.7m
Operating profit
NOK 2.1m
Equity
NOK 2.1m
Est. value
NOK 6.5m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.1%
Weak
Equity as a share of total capital

Who owns KULLERØDSVINGEN AS?

B1-PROSJEKT AS
KULLERØDSVINGEN AS
NOK 26.7m rev. · NOK 2.1m profit

KULLERØDSVINGEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KULLERØDSVINGEN AS

Who owns KULLERØDSVINGEN AS?

B1-PROSJEKT AS is the largest registered owner, with 100.0%.

What is the revenue of KULLERØDSVINGEN AS?

KULLERØDSVINGEN AS had revenue of NOK 26.7m in 2025.

Who is the general manager of KULLERØDSVINGEN AS?

Reidar Vårdal is registered as general manager of KULLERØDSVINGEN AS.

Where is KULLERØDSVINGEN AS based?

KULLERØDSVINGEN AS has its business address in Barkåker.

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.