BIZTRAC BETA
Computer consultancy and computer facilities management activities

KASYDRA AS

Org. no. 814253252 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −63,000
Equity NOK 1.5m
Incorporated 2014
Share capital NOK 500,000

Signals

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

KASYDRA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 814253252. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2014. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Tjenester (rådgivning) innenfor IT, økonomi og finans, forvaltning av egen kapital gjennom deltagelse i annen virksomhet, plassering i finansielle instrumenter og realkapital, samt annen tjenesteyting/virksomhet som måtte oppstå, herunder handel og annet som naturlig faller sammen med dette, delta i andre selskaper, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2025

Operating profit
NOK −63,000
Equity
NOK 1.5m
Est. value
NOK 11.2m

Financial health · 2025

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

Who owns KASYDRA AS?

DAG HALLE BRÆKKEN
KASYDRA AS
· NOK −63,000 profit

KASYDRA AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about KASYDRA AS

Who owns KASYDRA AS?

DAG HALLE BRÆKKEN is the largest registered owner, with 94.0%.

Who is the general manager of KASYDRA AS?

Dag Halle Brækken is registered as general manager of KASYDRA AS.

Where is KASYDRA AS based?

KASYDRA AS has its business address in Trondheim.

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.