BIZTRAC BETA
Buying and selling of own real estate

VIFA EIENDOM AS

Org. no. 924728795 Limited company (AS) Birkenes Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 84,000
Operating profit NOK −17,000
Equity NOK −7,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−7k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−17k kr).

VIFA EIENDOM AS is registered as a limited company in Birkenes, Agder with organisation number 924728795. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 84,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2024

Revenue
NOK 84,000
Operating profit
NOK −17,000
Equity
NOK −7,000

Financial health · 2024

Liquidity
0.38
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VIFA EIENDOM AS?

FRODE FAREMO VIMME
VIFA EIENDOM AS
NOK 84,000 rev. · NOK −17,000 profit

VIFA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIFA EIENDOM AS

Who owns VIFA EIENDOM AS?

FRODE FAREMO VIMME is the largest registered owner, with 50.0%.

What is the revenue of VIFA EIENDOM AS?

VIFA EIENDOM AS had revenue of NOK 84,000 in 2024.

Who is the general manager of VIFA EIENDOM AS?

Frode Faremo Vimme is registered as general manager of VIFA EIENDOM AS.

Where is VIFA EIENDOM AS based?

VIFA EIENDOM AS has its business address in Birkeland.

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.