BIZTRAC BETA
Combined facilities support activities

JENSEN DRIFT OG VEDLIKEHOLD AS

Org. no. 926038281 Limited company (AS) Holmestrand Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 14,000
Equity NOK 406,000
Incorporated 2020
Share capital NOK 30,000

JENSEN DRIFT OG VEDLIKEHOLD AS is registered as a limited company in Holmestrand, Vestfold with organisation number 926038281. 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 30 shares. The company's stated purpose is: “Drift og vedlikeholdstjenester på bygg og anlegg.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 14,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 14,000
Equity
NOK 406,000
Est. value
NOK 286,000

Financial health · 2025

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

Who owns JENSEN DRIFT OG VEDLIKEHOLD AS?

GEIR ARNE JENSEN
JENSEN DRIFT OG VEDLIKEHOLD AS
NOK 1.1m rev. · NOK 14,000 profit

JENSEN DRIFT OG VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JENSEN DRIFT OG VEDLIKEHOLD AS

Who owns JENSEN DRIFT OG VEDLIKEHOLD AS?

GEIR ARNE JENSEN is the largest registered owner, with 100.0%.

What is the revenue of JENSEN DRIFT OG VEDLIKEHOLD AS?

JENSEN DRIFT OG VEDLIKEHOLD AS had revenue of NOK 1.1m in 2025.

Who is the general manager of JENSEN DRIFT OG VEDLIKEHOLD AS?

Geir Arne Jensen is registered as general manager of JENSEN DRIFT OG VEDLIKEHOLD AS.

Where is JENSEN DRIFT OG VEDLIKEHOLD AS based?

JENSEN DRIFT OG VEDLIKEHOLD AS has its business address in Holmestrand.

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.