biztrac. BETA
COMPANY REGISTER PROFILE
986203672 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

AGDENES FYR AS

Org. no. 986203672 Limited company (AS) Trondheim Incorporated 2003 Active
Ownership graph ↗
Operating profit NOK −298,000
Equity NOK −5.7m
Incorporated 2003
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−5,7 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−298k kr).

AGDENES FYR AS is registered as a limited company in Trondheim, Trøndelag with organisation number 986203672. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2003. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Å eie og drive eiendom og alt som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −298,000
▲ +50 %
Equity
NOK −5.7m
▼ −18 %

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
-4.3%
Not satisfactory
Return on total assets
Solidity
-82.6%
Weak
Equity as a share of total capital

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

Who owns AGDENES FYR AS?

AGDENES FYR AS
· NOK −298,000 profit

AGDENES FYR AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about AGDENES FYR AS

Who owns AGDENES FYR AS?

NIDAROS SPAREBANK is the largest registered owner, with 100.0%.

Who is the general manager of AGDENES FYR AS?

Bjørn Arne Riise is registered as general manager of AGDENES FYR AS.

Where is AGDENES FYR AS based?

AGDENES FYR AS has its business address in Klæbu.

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

Report a problem

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