BIZTRAC BETA
Combined facilities support activities

DRIFTSTJENESTER AS

Org. no. 926039024 Limited company (AS) Enebakk Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 208,000
Operating profit NOK 60,000
Equity NOK 429,000
Incorporated 2020
Share capital NOK 30,000

DRIFTSTJENESTER AS is registered as a limited company in Enebakk, Akershus with organisation number 926039024. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Forretningsvirksomhet innen vaktmestertjenester, vedlikehold og ettersyn av fast eiendom og andre produkter og tjenester som naturlig hører til dette, herunder å delta iandre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 208,000 in revenue and NOK 60,000 in operating profit.

Key figures · 2025

Revenue
NOK 208,000
Operating profit
NOK 60,000
Equity
NOK 429,000
Est. value
NOK 461,000

Financial health · 2025

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

Who owns DRIFTSTJENESTER AS?

ANDERS RUUD
DRIFTSTJENESTER AS
NOK 208,000 rev. · NOK 60,000 profit

DRIFTSTJENESTER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRIFTSTJENESTER AS

Who owns DRIFTSTJENESTER AS?

ANDERS RUUD is the largest registered owner, with 50.0%.

What is the revenue of DRIFTSTJENESTER AS?

DRIFTSTJENESTER AS had revenue of NOK 208,000 in 2025.

Who is the general manager of DRIFTSTJENESTER AS?

Anders Ruud is registered as general manager of DRIFTSTJENESTER AS.

Where is DRIFTSTJENESTER AS based?

DRIFTSTJENESTER AS has its business address in Flateby.

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.