BIZTRAC BETA
Growing of grapes

SLINDE VINGARD AS

Org. no. 977047285 Limited company (AS) Sogndal Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 313,000
Operating profit NOK 43,000
Equity NOK −273,000
Incorporated 1996
Share capital NOK 220,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−273k kr).

SLINDE VINGARD AS is registered as a limited company in Sogndal, Vestland with organisation number 977047285. The business is classified under growing of grapes (NACE 01.210). The company was incorporated in 1996. Registered share capital is NOK 220,000, divided into 220 shares. The company's stated purpose is: “Vingårdsdrift, kulturopplevelse, foto og det hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 313,000 in revenue and NOK 43,000 in operating profit.

Key figures · 2025

Revenue
NOK 313,000
Operating profit
NOK 43,000
Equity
NOK −273,000
Est. value
NOK 167,000

Financial health · 2025

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-36.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SLINDE VINGARD AS?

HALLDIS SOLVEIG NEDREBØ
SLINDE VINGARD AS
NOK 313,000 rev. · NOK 43,000 profit

SLINDE VINGARD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SLINDE VINGARD AS

Who owns SLINDE VINGARD AS?

HALLDIS SOLVEIG NEDREBØ is the largest registered owner, with 50.0%.

What is the revenue of SLINDE VINGARD AS?

SLINDE VINGARD AS had revenue of NOK 313,000 in 2025.

Who is the general manager of SLINDE VINGARD AS?

Bjørn Ove Bergum is registered as general manager of SLINDE VINGARD AS.

Where is SLINDE VINGARD AS based?

SLINDE VINGARD AS has its business address in Slinda.

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.