BIZTRAC BETA
Manufacture of solid fuels from vegetable biomass

SVINNDAL BYGDESERVICE AS

Org. no. 931061518 Limited company (AS) Våler Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 805,000
Operating profit NOK 24,000
Equity NOK 279,000
Incorporated 2023
Share capital NOK 100,000

SVINNDAL BYGDESERVICE AS is registered as a limited company in Våler, Østfold with organisation number 931061518. The business is classified under manufacture of solid fuels from vegetable biomass (NACE 16.260). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg av ved - tjenester til landbruk - vaktmestertjenester - transportoppdrag - gravearbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 805,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 805,000
Operating profit
NOK 24,000
Equity
NOK 279,000
Est. value
NOK 222,000

Financial health · 2025

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

Who owns SVINNDAL BYGDESERVICE AS?

HARRY WESTGÅRD
SVINNDAL BYGDESERVICE AS
NOK 805,000 rev. · NOK 24,000 profit

SVINNDAL BYGDESERVICE AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SVINNDAL BYGDESERVICE AS

Who owns SVINNDAL BYGDESERVICE AS?

HARRY WESTGÅRD is the largest registered owner, with 62.0%.

What is the revenue of SVINNDAL BYGDESERVICE AS?

SVINNDAL BYGDESERVICE AS had revenue of NOK 805,000 in 2025.

Who is the general manager of SVINNDAL BYGDESERVICE AS?

Kajsa Stina Westgård Sukke is registered as general manager of SVINNDAL BYGDESERVICE AS.

Where is SVINNDAL BYGDESERVICE AS based?

SVINNDAL BYGDESERVICE AS has its business address in Svinndal.

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.