biztrac. BETA
COMPANY REGISTER PROFILE
913925807 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

TB-REGNSKAP AS

Org. no. 913925807 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 12,000
Operating profit NOK −15,000
Equity NOK −35,000
Incorporated 2014
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−35k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

TB-REGNSKAP AS is registered as a limited company in Oslo, Oslo with organisation number 913925807. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulentvirksomhet rettet mot selskapers regnskap og økonomi.”. The most recent filed accounts, for the 2025 financial year, show NOK 12,000 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 12,000
Operating profit
NOK −15,000
▼ −812 %
Equity
NOK −35,000
▼ −72 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-2138.1%
Weak
Equity as a share of total capital

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

Who owns TB-REGNSKAP AS?

TB-REGNSKAP AS
NOK 12,000 rev. · NOK −15,000 profit

TB-REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TB-REGNSKAP AS

Who owns TB-REGNSKAP AS?

Tor Bækkevold is the largest registered owner, with 96.7%.

What is the revenue of TB-REGNSKAP AS?

TB-REGNSKAP AS had revenue of NOK 12,000 in 2025.

Where is TB-REGNSKAP AS based?

TB-REGNSKAP AS has its business address in Oslo.

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.