BIZTRAC BETA
Business and other management consultancy activities

THOMAS VERVIK HOLDING AS

Org. no. 913960106 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 18,000
Equity NOK 5.3m
Incorporated 2014
Share capital NOK 30,000

THOMAS VERVIK HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 913960106. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Selskapet skal investere og drive rådgivning innenfor oppstart av nye selskaper som driver med IT teknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 18,000
Equity
NOK 5.3m
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns THOMAS VERVIK HOLDING AS?

THOMAS RENE VERVIK HAUGEN
THOMAS VERVIK HOLDING AS
NOK 1.0m rev. · NOK 18,000 profit

THOMAS VERVIK HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does THOMAS VERVIK HOLDING AS own?

THOMAS VERVIK HOLDING AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about THOMAS VERVIK HOLDING AS

Who owns THOMAS VERVIK HOLDING AS?

THOMAS RENE VERVIK HAUGEN is the largest registered owner, with 100.0%.

What is the revenue of THOMAS VERVIK HOLDING AS?

THOMAS VERVIK HOLDING AS had revenue of NOK 1.0m in 2025.

Where is THOMAS VERVIK HOLDING AS based?

THOMAS VERVIK HOLDING AS has its business address in Bergen.

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.