BIZTRAC BETA
Other software publishing

DAGENDIN NO AS

Org. no. 982168627 Limited company (AS) Stryn Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 138,000
Operating profit NOK 19,000
Equity NOK 193,000
Incorporated 2000
Share capital NOK 300,000

DAGENDIN NO AS is registered as a limited company in Stryn, Vestland with organisation number 982168627. The business is classified under other software publishing (NACE 58.290). The company was incorporated in 2000. Registered share capital is NOK 300,000, divided into 3000000 shares. The company's stated purpose is: “Fremstilling/salg av databaser/internettløysinger, herunder DAGENDIN.NO og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 138,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 138,000
Operating profit
NOK 19,000
Equity
NOK 193,000
Est. value
NOK 235,000

Financial health · 2025

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

Who owns DAGENDIN NO AS?

TOR ÅGE BERGLID
DAGENDIN NO AS
NOK 138,000 rev. · NOK 19,000 profit

DAGENDIN NO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAGENDIN NO AS

Who owns DAGENDIN NO AS?

TOR ÅGE BERGLID is the largest registered owner, with 100.0%.

What is the revenue of DAGENDIN NO AS?

DAGENDIN NO AS had revenue of NOK 138,000 in 2025.

Who is the general manager of DAGENDIN NO AS?

Tor Åge Berglid is registered as general manager of DAGENDIN NO AS.

Where is DAGENDIN NO AS based?

DAGENDIN NO AS has its business address in Blaksæter.

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.