biztrac. BETA
COMPANY REGISTER PROFILE
928960013 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Growing of grapes

VILLSTRÅ VINMAKERI SA

Org. no. 928960013 Co-operation (SA) Færder Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −43,000
Equity NOK 107,000
Incorporated 2022

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−43k kr).

VILLSTRÅ VINMAKERI SA is registered as a co-operation in Færder, Vestfold with organisation number 928960013. The business is classified under growing of grapes (NACE 01.210). The company was incorporated in 2022. The company's stated purpose is: “Foretaket skal drive jordbruk - Dyrking av druer (A 01.210). Industri - Produksjon av vin (C 11.02). Foretaket har til formål å dyrke druer, produsere vin og i tillegg skape en arena for kunnskap og kultur omkring vin.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −43,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −43,000
Equity
NOK 107,000
Est. value
NOK 101,000

Financial health · 2025

Liquidity
-1850.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns VILLSTRÅ VINMAKERI SA?

No shareholders are registered for VILLSTRÅ VINMAKERI SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about VILLSTRÅ VINMAKERI SA

What is the revenue of VILLSTRÅ VINMAKERI SA?

VILLSTRÅ VINMAKERI SA had revenue of NOK 0 in 2025.

Who is the general manager of VILLSTRÅ VINMAKERI SA?

Kjersti Førendal is registered as general manager of VILLSTRÅ VINMAKERI SA.

Where is VILLSTRÅ VINMAKERI SA based?

VILLSTRÅ VINMAKERI SA has its business address in Tjøme.

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.