BIZTRAC BETA
Legal activities

INDEM ADVOKATFIRMA AS

Org. no. 816316952 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 5.3m
Operating profit NOK −617,000
Equity NOK −2.6m
Incorporated 2015
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,6 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−617k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

INDEM ADVOKATFIRMA AS is registered as a limited company in Oslo, Oslo with organisation number 816316952. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å yte juridisk rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.3m in revenue and NOK −617,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.3m
Operating profit
NOK −617,000
Equity
NOK −2.6m

Financial health · 2025

Liquidity
0.46
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-117.5%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns INDEM ADVOKATFIRMA AS?

INDEM AS
INDEM ADVOKATFIRMA AS
NOK 5.3m rev. · NOK −617,000 profit

INDEM ADVOKATFIRMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INDEM ADVOKATFIRMA AS

Who owns INDEM ADVOKATFIRMA AS?

INDEM AS is the largest registered owner, with 100.0%.

What is the revenue of INDEM ADVOKATFIRMA AS?

INDEM ADVOKATFIRMA AS had revenue of NOK 5.3m in 2025.

Where is INDEM ADVOKATFIRMA AS based?

INDEM ADVOKATFIRMA AS has its business address in Oslo.

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.