BIZTRAC BETA
Accounting and bookkeeping

AGENDA REGNSKAP AS

Org. no. 996756238 Limited company (AS) Fredrikstad Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 5.8m
Operating profit NOK 1.9m
Equity NOK 18.1m
Incorporated 2011
Employees 6
Share capital NOK 100,000

AGENDA REGNSKAP AS is registered as a limited company in Fredrikstad, Østfold with organisation number 996756238. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2011 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Regnskapsføring og det som dertil hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.8m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 5.8m
Operating profit
NOK 1.9m
Equity
NOK 18.1m
Est. value
NOK 18.4m

Financial health · 2025

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

Who owns AGENDA REGNSKAP AS?

CHRISTIAN BØRGE TVETE
AGENDA REGNSKAP AS
NOK 5.8m rev. · NOK 1.9m profit

AGENDA REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AGENDA REGNSKAP AS own?

AGENDA REGNSKAP AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AGENDA REGNSKAP AS

Who owns AGENDA REGNSKAP AS?

CHRISTIAN BØRGE TVETE is the largest registered owner, with 100.0%.

What is the revenue of AGENDA REGNSKAP AS?

AGENDA REGNSKAP AS had revenue of NOK 5.8m in 2025.

Who is the general manager of AGENDA REGNSKAP AS?

Christian Børge Tvete is registered as general manager of AGENDA REGNSKAP AS.

Where is AGENDA REGNSKAP AS based?

AGENDA REGNSKAP AS has its business address in Fredrikstad.

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.