BIZTRAC BETA
Site preparation

VESTBY BYGDESERVICE AS

Org. no. 933118991 Limited company (AS) Trysil Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −355,000
Equity NOK 565,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

VESTBY BYGDESERVICE AS is registered as a limited company in Trysil, Innlandet with organisation number 933118991. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utføre mindre entreprenørarbeider, levere tjenester til landbruk, skogbruk, byggebransjen, turistnæring og privatpersoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −355,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK −355,000
Equity
NOK 565,000
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns VESTBY BYGDESERVICE AS?

KENT EVENSEN
VESTBY BYGDESERVICE AS
NOK 2.4m rev. · NOK −355,000 profit

VESTBY BYGDESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTBY BYGDESERVICE AS

Who owns VESTBY BYGDESERVICE AS?

KENT EVENSEN is the largest registered owner, with 100.0%.

What is the revenue of VESTBY BYGDESERVICE AS?

VESTBY BYGDESERVICE AS had revenue of NOK 2.4m in 2025.

Who is the general manager of VESTBY BYGDESERVICE AS?

Kent Evensen is registered as general manager of VESTBY BYGDESERVICE AS.

Where is VESTBY BYGDESERVICE AS based?

VESTBY BYGDESERVICE AS has its business address in Trysil.

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.