biztrac. BETA
COMPANY REGISTER PROFILE
917712522 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

VRDI AS

Org. no. 917712522 Limited company (AS) Bergen Incorporated 2016 Active
Revenue 2025 NOK 1.1m
Operating profit NOK −2,000
Equity NOK 560,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

VRDI AS is registered as a limited company in Bergen, Vestland with organisation number 917712522. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å drive konsulent-, rådgivnings- og styrevirksomhet innen økonomi, virksomhetsutvikling, ledelse og administrasjon, samt investeringer og annen virksomhet som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
▲ +0 %
Operating profit
NOK −2,000
▲ +0 %
Equity
NOK 560,000
▲ +0 %
Est. value
NOK 503,000

Financial health · 2025

Liquidity
2.48
Very good
Current assets ÷ current liabilities
Profitability
21.2%
Very good
Return on total assets
Solidity
59.7%
Very good
Equity as a share of total capital

Who owns VRDI AS?

VRDI AS
NOK 1.1m rev. · NOK −2,000 profit

VRDI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VRDI AS

Who owns VRDI AS?

Else-Marit Haugland is the largest registered owner, with 100.0%.

What is the revenue of VRDI AS?

VRDI AS had revenue of NOK 1.1m in 2025.

Who is the general manager of VRDI AS?

Else-Marit Haugland is registered as general manager of VRDI AS.

Where is VRDI AS based?

VRDI AS has its business address in Arnatveit.

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.