BIZTRAC BETA
Combined facilities support activities

EVEN DYVE FON AS

Org. no. 928924068 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 549,000
Equity NOK 1.5m
Incorporated 2022
Share capital NOK 30,000

EVEN DYVE FON AS is registered as a limited company in Drammen, Buskerud with organisation number 928924068. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drift og vedlikehold av eiendom, vaktmestertjenester, anleggsgartner virksomhet, vinter- og sommervedlikehold. I tillegg skal det være anledning til kjøp og salg av aksjer, utleie av eiendom samt det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 549,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 549,000
Equity
NOK 1.5m
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns EVEN DYVE FON AS?

EVEN DYVE FON
EVEN DYVE FON AS
NOK 4.3m rev. · NOK 549,000 profit

EVEN DYVE FON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EVEN DYVE FON AS

Who owns EVEN DYVE FON AS?

EVEN DYVE FON is the largest registered owner, with 100.0%.

What is the revenue of EVEN DYVE FON AS?

EVEN DYVE FON AS had revenue of NOK 4.3m in 2025.

Who is the general manager of EVEN DYVE FON AS?

Even Dyve Fon is registered as general manager of EVEN DYVE FON AS.

Where is EVEN DYVE FON AS based?

EVEN DYVE FON AS has its business address in Svelvik.

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.