BIZTRAC BETA
COMPANY REGISTER PROFILE
982812569 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Freight transport by road

TVERLI SJÅFØR & MONTØR

Org. no. 982812569 Sole proprietorship (ENK) Bærum Active
Ownership graph ↗
Revenue 2025 NOK 9.5m
Operating profit NOK 422,000
Equity NOK 64,000
Employees 10

TVERLI SJÅFØR & MONTØR is registered as a sole proprietorship in Bærum, Akershus with organisation number 982812569. The business is classified under freight transport by road (NACE 49.410). The company has 10 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 9.5m in revenue and NOK 422,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.5m
Operating profit
NOK 422,000
Equity
NOK 64,000
Est. value
NOK 1.4m

Financial health · 2025

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

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

Who owns TVERLI SJÅFØR & MONTØR?

No shareholders are registered for TVERLI SJÅFØR & MONTØR in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about TVERLI SJÅFØR & MONTØR

What is the revenue of TVERLI SJÅFØR & MONTØR?

TVERLI SJÅFØR & MONTØR had revenue of NOK 9.5m in 2025.

Where is TVERLI SJÅFØR & MONTØR based?

TVERLI SJÅFØR & MONTØR has its business address in Rykkinn.

Property

Business address Munins vei 13, 1348 Rykkinn
Cadastral unit 3201-93/20/0/0
Building Enebolig · 1 unit

6 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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.