BIZTRAC BETA
Legal activities

ADVOKAT ERLING HØYTE AS

Org. no. 925498955 Limited company (AS) Frogn Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 2.0m
Equity NOK 8.0m
Incorporated 2020
Share capital NOK 30,000

ADVOKAT ERLING HØYTE AS is registered as a limited company in Frogn, Akershus with organisation number 925498955. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1 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 3.9m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 2.0m
Equity
NOK 8.0m
Est. value
NOK 11.8m

Financial health · 2025

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

Who owns ADVOKAT ERLING HØYTE AS?

ERLING HØYTE
ADVOKAT ERLING HØYTE AS
NOK 3.9m rev. · NOK 2.0m profit

ADVOKAT ERLING HØYTE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ADVOKAT ERLING HØYTE AS own?

ADVOKAT ERLING HØYTE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ADVOKAT ERLING HØYTE AS

Who owns ADVOKAT ERLING HØYTE AS?

ERLING HØYTE is the largest registered owner, with 100.0%.

What is the revenue of ADVOKAT ERLING HØYTE AS?

ADVOKAT ERLING HØYTE AS had revenue of NOK 3.9m in 2025.

Who is the general manager of ADVOKAT ERLING HØYTE AS?

Erling Høyte is registered as general manager of ADVOKAT ERLING HØYTE AS.

Where is ADVOKAT ERLING HØYTE AS based?

ADVOKAT ERLING HØYTE AS has its business address in Drøbak.

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.