BIZTRAC BETA
Legal activities

ADVOKATHUSET VELAND OG THINGVOLD AS

Org. no. 916797524 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 9.3m
Operating profit NOK 2.6m
Equity NOK 2.0m
Incorporated 2016
Employees 8
Share capital NOK 30,000

ADVOKATHUSET VELAND OG THINGVOLD AS is registered as a limited company in Stavanger, Rogaland with organisation number 916797524. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2016 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Advokatvirksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 9.3m in revenue and NOK 2.6m in operating profit.

Key figures · 2025

Revenue
NOK 9.3m
Operating profit
NOK 2.6m
Equity
NOK 2.0m
Est. value
NOK 10.1m

Financial health · 2025

Liquidity
1.63
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.7%
Good
Equity as a share of total capital

Who owns ADVOKATHUSET VELAND OG THINGVOLD AS?

NORAAS HOLDING AS
ADVOKATHUSET VELAND OG THINGVOLD AS
NOK 9.3m rev. · NOK 2.6m profit

ADVOKATHUSET VELAND OG THINGVOLD AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATHUSET VELAND OG THINGVOLD AS

Who owns ADVOKATHUSET VELAND OG THINGVOLD AS?

NORAAS HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of ADVOKATHUSET VELAND OG THINGVOLD AS?

ADVOKATHUSET VELAND OG THINGVOLD AS had revenue of NOK 9.3m in 2025.

Who is the general manager of ADVOKATHUSET VELAND OG THINGVOLD AS?

Håkon Noraas is registered as general manager of ADVOKATHUSET VELAND OG THINGVOLD AS.

Where is ADVOKATHUSET VELAND OG THINGVOLD AS based?

ADVOKATHUSET VELAND OG THINGVOLD AS has its business address in Stavanger.

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.