BIZTRAC BETA
Joinery installation

ARIFI VEDLIKEHOLD AS

Org. no. 832069442 Limited company (AS) Ullensvang Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 236,000
Equity NOK 288,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-03-20 Adresseendring registrert 2026-03-20.

ARIFI VEDLIKEHOLD AS is registered as a limited company in Ullensvang, Vestland with organisation number 832069442. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Vedlikehold og rehabilitering for bygg og industri, herunder maling, stillas, snekkerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 236,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 236,000
Equity
NOK 288,000
Est. value
NOK 839,000

Financial health · 2025

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

Who owns ARIFI VEDLIKEHOLD AS?

ARIFI HOLDING AS
ARIFI VEDLIKEHOLD AS
NOK 1.6m rev. · NOK 236,000 profit

ARIFI VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ARIFI VEDLIKEHOLD AS

Who owns ARIFI VEDLIKEHOLD AS?

ARIFI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ARIFI VEDLIKEHOLD AS?

ARIFI VEDLIKEHOLD AS had revenue of NOK 1.6m in 2025.

Who is the general manager of ARIFI VEDLIKEHOLD AS?

Valdet Arifi is registered as general manager of ARIFI VEDLIKEHOLD AS.

Where is ARIFI VEDLIKEHOLD AS based?

ARIFI VEDLIKEHOLD AS has its business address in Odda.

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.