biztrac. BETA
COMPANY REGISTER PROFILE
913942221 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

VEGUSDAL BYGDESERVICE AS

Org. no. 913942221 Limited company (AS) Birkenes Incorporated 2014 Active
Revenue 2025 NOK 1.2m
Operating profit NOK 138,000
Equity NOK 934,000
Incorporated 2014
Share capital NOK 30,000

VEGUSDAL BYGDESERVICE AS is registered as a limited company in Birkenes, Agder with organisation number 913942221. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Anleggsarbeider, brøyting, samt utleie av handverkertjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 138,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
▼ −41 %
Operating profit
NOK 138,000
▼ −32 %
Equity
NOK 934,000
▲ +6 %
Est. value
NOK 840,000

Financial health · 2025

Liquidity
5.73
Very good
Current assets ÷ current liabilities
Profitability
11.3%
Good
Return on total assets
Solidity
78.5%
Very good
Equity as a share of total capital

Who owns VEGUSDAL BYGDESERVICE AS?

VEGUSDAL BYGDESERVICE AS
NOK 1.2m rev. · NOK 138,000 profit

VEGUSDAL BYGDESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEGUSDAL BYGDESERVICE AS

Who owns VEGUSDAL BYGDESERVICE AS?

Nils Lennart Skåre Fersnes is the largest registered owner, with 100.0%.

What is the revenue of VEGUSDAL BYGDESERVICE AS?

VEGUSDAL BYGDESERVICE AS had revenue of NOK 1.2m in 2025.

Who is the general manager of VEGUSDAL BYGDESERVICE AS?

Nils Lennart Skåre Fersnes is registered as general manager of VEGUSDAL BYGDESERVICE AS.

Where is VEGUSDAL BYGDESERVICE AS based?

VEGUSDAL BYGDESERVICE AS has its business address in Evje.

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.