BIZTRAC BETA
Business and other management consultancy activities

DRIFT & KOMMUNIKASJON AS

Org. no. 816273072 Limited company (AS) Tønsberg Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 400,000
Operating profit NOK 50,000
Equity NOK 212,000
Incorporated 2015
Share capital NOK 30,000

DRIFT & KOMMUNIKASJON AS is registered as a limited company in Tønsberg, Vestfold with organisation number 816273072. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av konsulenttjenester - kjøp/salg av fast eiendom og andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 400,000 in revenue and NOK 50,000 in operating profit.

Key figures · 2025

Revenue
NOK 400,000
Operating profit
NOK 50,000
Equity
NOK 212,000
Est. value
NOK 405,000

Financial health · 2025

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

Who owns DRIFT & KOMMUNIKASJON AS?

LORVIK HOLDING AS
DRIFT & KOMMUNIKASJON AS
NOK 400,000 rev. · NOK 50,000 profit

DRIFT & KOMMUNIKASJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRIFT & KOMMUNIKASJON AS

Who owns DRIFT & KOMMUNIKASJON AS?

LORVIK HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of DRIFT & KOMMUNIKASJON AS?

DRIFT & KOMMUNIKASJON AS had revenue of NOK 400,000 in 2025.

Who is the general manager of DRIFT & KOMMUNIKASJON AS?

Per Joar Lorvik is registered as general manager of DRIFT & KOMMUNIKASJON AS.

Where is DRIFT & KOMMUNIKASJON AS based?

DRIFT & KOMMUNIKASJON AS has its business address in Tolvsrød.

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.