BIZTRAC BETA
Rental and operating of own or leased real estate

ADVOKATGÅRDEN LILLEHAMMER AS

Org. no. 980728978 Limited company (AS) Lillehammer Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 1.4m
Equity NOK 2.0m
Incorporated 1999
Share capital NOK 250,000

ADVOKATGÅRDEN LILLEHAMMER AS is registered as a limited company in Lillehammer, Innlandet with organisation number 980728978. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Eie og drive fast eiendom i Storgaten 121 i Lillehammer.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 1.4m
Equity
NOK 2.0m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns ADVOKATGÅRDEN LILLEHAMMER AS?

GUNNAR KRISTEN HAGEN
ADVOKATGÅRDEN LILLEHAMMER AS
NOK 2.2m rev. · NOK 1.4m profit

ADVOKATGÅRDEN LILLEHAMMER AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATGÅRDEN LILLEHAMMER AS

Who owns ADVOKATGÅRDEN LILLEHAMMER AS?

GUNNAR KRISTEN HAGEN is the largest registered owner, with 20.0%.

What is the revenue of ADVOKATGÅRDEN LILLEHAMMER AS?

ADVOKATGÅRDEN LILLEHAMMER AS had revenue of NOK 2.2m in 2024.

Who is the general manager of ADVOKATGÅRDEN LILLEHAMMER AS?

Gunnar Kristen Hagen is registered as general manager of ADVOKATGÅRDEN LILLEHAMMER AS.

Where is ADVOKATGÅRDEN LILLEHAMMER AS based?

ADVOKATGÅRDEN LILLEHAMMER AS has its business address in Lillehammer.

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.