biztrac. BETA
COMPANY REGISTER PROFILE
912313255 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Legal activities

ZENIT ADVOKATER AS

Org. no. 912313255 Limited company (AS) Tønsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 14.3m
Operating profit NOK 4.0m
Equity NOK 153,000
Incorporated 2013
Employees 6
Share capital NOK 150,000

ZENIT ADVOKATER AS is registered as a limited company in Tønsberg, Vestfold with organisation number 912313255. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2013 and has 6 registered employees. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Advokatvirksomhet samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.3m in revenue and NOK 4.0m in operating profit.

Former names: ADVOKATFIRMAET WIKSTØL MATRE AS, WIKSTØL MATRE JENSEN ADVOKATFIRMA AS

Key figures · 2025

Revenue
NOK 14.3m
▲ +22 %
Operating profit
NOK 4.0m
▲ +185 %
Equity
NOK 153,000
▲ +1 %
Est. value
NOK 11.9m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
79.5%
Very good
Return on total assets
Solidity
2.3%
Not satisfactory
Equity as a share of total capital

Who owns ZENIT ADVOKATER AS?

ZENIT ADVOKATER AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ZENIT ADVOKATER AS

Who owns ZENIT ADVOKATER AS?

ADVOKAT SJÅVIK HOLDING AS is the largest registered owner, with 25.0%.

What is the revenue of ZENIT ADVOKATER AS?

ZENIT ADVOKATER AS had revenue of NOK 14.3m in 2025.

Who is the general manager of ZENIT ADVOKATER AS?

Pål Skarnes Jensen is registered as general manager of ZENIT ADVOKATER AS.

Where is ZENIT ADVOKATER AS based?

ZENIT ADVOKATER AS has its business address in Tønsberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.