BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

VILAPEMA AS

Org. no. 921697406 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK −99,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

VILAPEMA AS is registered as a limited company in Bærum, Akershus with organisation number 921697406. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Konsulent - og investeringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK −99,000

Financial health · 2025

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

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

Who owns VILAPEMA AS?

LARS ANDREAS MIDTGAARD
VILAPEMA AS
NOK 0 rev. · NOK −7,000 profit

VILAPEMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VILAPEMA AS

Who owns VILAPEMA AS?

LARS ANDREAS MIDTGAARD is the largest registered owner, with 100.0%.

What is the revenue of VILAPEMA AS?

VILAPEMA AS had revenue of NOK 0 in 2025.

Who is the general manager of VILAPEMA AS?

Lars Andreas Midtgaard is registered as general manager of VILAPEMA AS.

Where is VILAPEMA AS based?

VILAPEMA AS has its business address in Høvik.

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.