BIZTRAC BETA
Legal activities

ADVOKAT TOVE NISSEN-SOLLIE AS

Org. no. 914948320 Limited company (AS) Larvik Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 116,000
Equity NOK 1.0m
Incorporated 2015
Share capital NOK 30,000

ADVOKAT TOVE NISSEN-SOLLIE AS is registered as a limited company in Larvik, Vestfold with organisation number 914948320. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenester som utøvende Advokat. Samt delta i annen virksomhet som har nærliggende tilknytning til hovedformålet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 116,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 116,000
Equity
NOK 1.0m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns ADVOKAT TOVE NISSEN-SOLLIE AS?

TOVE NISSEN-SOLLIE
ADVOKAT TOVE NISSEN-SOLLIE AS
NOK 2.1m rev. · NOK 116,000 profit

ADVOKAT TOVE NISSEN-SOLLIE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKAT TOVE NISSEN-SOLLIE AS

Who owns ADVOKAT TOVE NISSEN-SOLLIE AS?

TOVE NISSEN-SOLLIE is the largest registered owner, with 100.0%.

What is the revenue of ADVOKAT TOVE NISSEN-SOLLIE AS?

ADVOKAT TOVE NISSEN-SOLLIE AS had revenue of NOK 2.1m in 2025.

Who is the general manager of ADVOKAT TOVE NISSEN-SOLLIE AS?

Tove Nissen-Sollie is registered as general manager of ADVOKAT TOVE NISSEN-SOLLIE AS.

Where is ADVOKAT TOVE NISSEN-SOLLIE AS based?

ADVOKAT TOVE NISSEN-SOLLIE AS has its business address in Larvik.

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.