BIZTRAC BETA
Legal activities

ADVOKATFIRMAET LYSØ AS

Org. no. 979393172 Limited company (AS) Namsos Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK −714,000
Equity NOK 520,000
Incorporated 1997
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−714k kr).

ADVOKATFIRMAET LYSØ AS is registered as a limited company in Namsos, Trøndelag with organisation number 979393172. The business is classified under legal activities (NACE 69.100). The company was incorporated in 1997. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utføre ordinære advokattjenester og andre tjenester som naturlig hører med til advokatvirksomheten.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK −714,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK −714,000
Equity
NOK 520,000
Est. value
NOK 3.5m

Financial health · 2025

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

Who owns ADVOKATFIRMAET LYSØ AS?

ENDRE GANSMO LYSØ
ADVOKATFIRMAET LYSØ AS
NOK 3.1m rev. · NOK −714,000 profit

ADVOKATFIRMAET LYSØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ADVOKATFIRMAET LYSØ AS

Who owns ADVOKATFIRMAET LYSØ AS?

ENDRE GANSMO LYSØ is the largest registered owner, with 100.0%.

What is the revenue of ADVOKATFIRMAET LYSØ AS?

ADVOKATFIRMAET LYSØ AS had revenue of NOK 3.1m in 2025.

Who is the general manager of ADVOKATFIRMAET LYSØ AS?

Endre Gansmo Lysø is registered as general manager of ADVOKATFIRMAET LYSØ AS.

Where is ADVOKATFIRMAET LYSØ AS based?

ADVOKATFIRMAET LYSØ AS has its business address in Namsos.

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.