BIZTRAC BETA
Rental and leasing of construction and civil engineering machinery and equipment

TB INVEST AS

Org. no. 911769204 Limited company (AS) Verdal Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 8,000
Equity NOK 3.5m
Incorporated 2013
Share capital NOK 200,000

TB INVEST AS is registered as a limited company in Verdal, Trøndelag with organisation number 911769204. The business is classified under rental and leasing of construction and civil engineering machinery and equipment (NACE 77.320). The company was incorporated in 2013. Registered share capital is NOK 200,000, divided into 30 shares. The company's stated purpose is: “Investeringer, utleie av driftsmidler, samt andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 8,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 8,000
Equity
NOK 3.5m
Est. value
NOK 1.8m

Financial health · 2024

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

Who owns TB INVEST AS?

NINA MERETE BAKKAN
TB INVEST AS
NOK 2.9m rev. · NOK 8,000 profit

TB INVEST AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TB INVEST AS own?

TB INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

TB INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about TB INVEST AS

Who owns TB INVEST AS?

NINA MERETE BAKKAN is the largest registered owner, with 50.0%.

What is the revenue of TB INVEST AS?

TB INVEST AS had revenue of NOK 2.9m in 2024.

Where is TB INVEST AS based?

TB INVEST AS has its business address in Verdal.

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.