biztrac. BETA
COMPANY REGISTER PROFILE
916918801 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠HLT ADVOKATFIRMA AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Legal activities

HLT ADVOKATFIRMA AS

Org. no. 916918801 Limited company (AS) Bergen Incorporated 2016 In liquidation
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 2.5m
Equity NOK 6.0m
Incorporated 2016
Share capital NOK 125,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Nylig endring 2026-10-07 Under avvikling registrert 2026-10-07.

HLT ADVOKATFIRMA AS is registered as a limited company in Bergen, Vestland with organisation number 916918801. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2016. Registered share capital is NOK 125,000, divided into 500 shares. The company's stated purpose is: “Advokatvirksomhet og det som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 2.5m in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
▼ −76 %
Operating profit
NOK 2.5m
▼ −63 %
Equity
NOK 6.0m
▼ −36 %
Est. value
NOK 16.8m

Financial health · 2025

Liquidity
222.29
Very good
Current assets ÷ current liabilities
Profitability
31.3%
Very good
Return on total assets
Solidity
99.6%
Very good
Equity as a share of total capital

Who owns HLT ADVOKATFIRMA AS?

HLT ADVOKATFIRMA AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about HLT ADVOKATFIRMA AS

Who owns HLT ADVOKATFIRMA AS?

ADVOKAT TUNGESVIK AS is the largest registered owner, with 16.8%.

What is the revenue of HLT ADVOKATFIRMA AS?

HLT ADVOKATFIRMA AS had revenue of NOK 4.8m in 2025.

Where is HLT ADVOKATFIRMA AS based?

HLT ADVOKATFIRMA AS has its business address in Fyllingsdalen.

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.