BIZTRAC BETA
Accounting and bookkeeping

2R DATA OG REGNSKAP AS

Org. no. 951240435 Limited company (AS) Lillestrøm Incorporated 1989 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 22,000
Equity NOK 481,000
Incorporated 1989
Share capital NOK 100,000

2R DATA OG REGNSKAP AS is registered as a limited company in Lillestrøm, Akershus with organisation number 951240435. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Selge EDB relatert utstyr og programvare, samt salg av tjenester relatert til elektronisk databehandling. Videre skal selskapet selge regnskapstjenester og økonomirådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 22,000
Equity
NOK 481,000
Est. value
NOK 346,000

Financial health · 2025

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
35.5%
Good
Equity as a share of total capital

Who owns 2R DATA OG REGNSKAP AS?

ESPEN MAGNE DAHL
2R DATA OG REGNSKAP AS
NOK 3.6m rev. · NOK 22,000 profit

2R DATA OG REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about 2R DATA OG REGNSKAP AS

Who owns 2R DATA OG REGNSKAP AS?

ESPEN MAGNE DAHL is the largest registered owner, with 56.0%.

What is the revenue of 2R DATA OG REGNSKAP AS?

2R DATA OG REGNSKAP AS had revenue of NOK 3.6m in 2025.

Who is the general manager of 2R DATA OG REGNSKAP AS?

Espen Magne Dahl is registered as general manager of 2R DATA OG REGNSKAP AS.

Where is 2R DATA OG REGNSKAP AS based?

2R DATA OG REGNSKAP AS has its business address in Lillestrøm.

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.