BIZTRAC BETA
COMPANY REGISTER PROFILE
993646091 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Other technical consultancy

OLSBERG LOGISTIKK AS

Org. no. 993646091 Limited company (AS) Modum Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 46,000
Operating profit NOK 19,000
Equity NOK −219,000
Incorporated 2009
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−219k kr).

OLSBERG LOGISTIKK AS is registered as a limited company in Modum, Buskerud with organisation number 993646091. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2009. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transport megling, ingeniør tjenester, investering i aksjer/fond/eiendom/annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 46,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2024

Revenue
NOK 46,000
Operating profit
NOK 19,000
Equity
NOK −219,000
Est. value
NOK 85,000

Financial health · 2024

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

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

Who owns OLSBERG LOGISTIKK AS?

NAZILJA OLSBERG
OLSBERG LOGISTIKK AS
NOK 46,000 rev. · NOK 19,000 profit

OLSBERG LOGISTIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OLSBERG LOGISTIKK AS

Who owns OLSBERG LOGISTIKK AS?

NAZILJA OLSBERG is the largest registered owner, with 51.0%.

What is the revenue of OLSBERG LOGISTIKK AS?

OLSBERG LOGISTIKK AS had revenue of NOK 46,000 in 2024.

Where is OLSBERG LOGISTIKK AS based?

OLSBERG LOGISTIKK AS has its business address in Geithus.

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.