BIZTRAC BETA
COMPANY REGISTER PROFILE
991439358 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Repair and maintenance of motor vehicles

TOBOS TRADING AS

Org. no. 991439358 Limited company (AS) Arendal Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 514,000
Operating profit NOK 11,000
Equity NOK 4.4m
Incorporated 2007
Share capital NOK 100,000

TOBOS TRADING AS is registered as a limited company in Arendal, Agder with organisation number 991439358. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Handel og utvikling og drift av fast eiendom og annen virksomhet som står i forbindelse med dette. Selskapet kan delta i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 514,000 in revenue and NOK 11,000 in operating profit.

Key figures · 2025

Revenue
NOK 514,000
▲ +79 %
Operating profit
NOK 11,000
▲ +108 %
Equity
NOK 4.4m
▲ +7 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
52.83
Very good
Current assets ÷ current liabilities
Profitability
7.5%
Satisfactory
Return on total assets
Solidity
96.3%
Very good
Equity as a share of total capital

Who owns TOBOS TRADING AS?

TOBOS TRADING AS
NOK 514,000 rev. · NOK 11,000 profit

TOBOS TRADING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TOBOS TRADING AS

Who owns TOBOS TRADING AS?

TOM MORTENSEN is the largest registered owner, with 100.0%.

What is the revenue of TOBOS TRADING AS?

TOBOS TRADING AS had revenue of NOK 514,000 in 2025.

Who is the general manager of TOBOS TRADING AS?

Tom Mortensen is registered as general manager of TOBOS TRADING AS.

Where is TOBOS TRADING AS based?

TOBOS TRADING AS has its business address in Færvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.