BIZTRAC BETA
COMPANY REGISTER PROFILE
985247013 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
In liquidation UPDATED 25.08.2026
DEKAR RETTSHJELP AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Other real estate activities on a fee or contract basis

DEKAR RETTSHJELP AS

Org. no. 985247013 Limited company (AS) Melhus Incorporated 2003 In liquidation
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −16,000
Equity NOK 879,000
Incorporated 2003
Share capital NOK 300,000

Signals

2 flags
  • Under avvikling Selskapet er under frivillig avvikling.
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).

DEKAR RETTSHJELP AS is registered as a limited company in Melhus, Trøndelag with organisation number 985247013. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2003. Registered share capital is NOK 300,000, divided into 100 shares. The company's stated purpose is: “Yte bistand innen eiendomsrelaterte saker samt deltakelse i selskaper som arbeider innen tilknyttede områder. Firmaet kan også produsere, kjøpe og selge kunst.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Former names: DEKAR AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 879,000

Who owns DEKAR RETTSHJELP AS?

ANITA OLSEN
DEKAR RETTSHJELP AS
NOK 0 rev. · NOK −16,000 profit

DEKAR RETTSHJELP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DEKAR RETTSHJELP AS

Who owns DEKAR RETTSHJELP AS?

ANITA OLSEN is the largest registered owner, with 100.0%.

What is the revenue of DEKAR RETTSHJELP AS?

DEKAR RETTSHJELP AS had revenue of NOK 0 in 2025.

Where is DEKAR RETTSHJELP AS based?

DEKAR RETTSHJELP AS has its business address in Melhus.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 25.08.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.