BIZTRAC BETA
Other real estate activities on a fee or contract basis

VERVET DRIFT AS

Org. no. 926647733 Limited company (AS) Tromsø Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −1.7m
Equity NOK 422,000
Incorporated 2021
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,7 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VERVET DRIFT AS is registered as a limited company in Tromsø, Troms with organisation number 926647733. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forvaltning, drift og vedlikehold av eiendom og infrastruktur, herunder vaktmestertjenester og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −1.7m in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −1.7m
Equity
NOK 422,000
Est. value
NOK 3.5m

Financial health · 2024

Liquidity
1.15
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.0%
Satisfactory
Equity as a share of total capital

Who owns VERVET DRIFT AS?

VERVET AS
VERVET DRIFT AS
NOK 2.2m rev. · NOK −1.7m profit

VERVET DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VERVET DRIFT AS

Who owns VERVET DRIFT AS?

VERVET AS is the largest registered owner, with 100.0%.

What is the revenue of VERVET DRIFT AS?

VERVET DRIFT AS had revenue of NOK 2.2m in 2025.

Where is VERVET DRIFT AS based?

VERVET DRIFT AS has its business address in Tromsø.

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.