biztrac. BETA
COMPANY REGISTER PROFILE
990948003 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

NT REGNSKAP AS

Org. no. 990948003 Limited company (AS) Lørenskog Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 87,000
Equity NOK 683,000
Incorporated 2007
Share capital NOK 100,000

NT REGNSKAP AS is registered as a limited company in Lørenskog, Akershus with organisation number 990948003. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Å drive regnskapsføring, rådgivning og annen virksomhet som naturlig står i forbindelse med dette. Selskapet skal også drive og delta i andre virksomheter med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 87,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
▼ −9 %
Operating profit
NOK 87,000
▼ −72 %
Equity
NOK 683,000
▼ −9 %
Est. value
NOK 910,000

Financial health · 2025

Liquidity
1.24
Satisfactory
Current assets ÷ current liabilities
Profitability
5.6%
Weak
Return on total assets
Solidity
46.4%
Very good
Equity as a share of total capital

Who owns NT REGNSKAP AS?

NT REGNSKAP AS
NOK 3.4m rev. · NOK 87,000 profit

NT REGNSKAP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NT REGNSKAP AS

Who owns NT REGNSKAP AS?

Dinh Trong Tran is the largest registered owner, with 100.0%.

What is the revenue of NT REGNSKAP AS?

NT REGNSKAP AS had revenue of NOK 3.4m in 2025.

Who is the general manager of NT REGNSKAP AS?

Dinh Trong Tran is registered as general manager of NT REGNSKAP AS.

Where is NT REGNSKAP AS based?

NT REGNSKAP AS has its business address in Lørenskog.

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.