BIZTRAC BETA
COMPANY REGISTER PROFILE
971083107 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Logging

LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold

Org. no. 971083107 Sole proprietorship (ENK) Oslo Active
Ownership graph ↗
Revenue 2025 NOK 120.1m
Operating profit NOK 36.1m
Equity NOK 86.1m
Employees 25

LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold is registered as a sole proprietorship in Oslo, Oslo with organisation number 971083107. The business is classified under logging (NACE 02.200). The company has 25 registered employees. The most recent filed accounts, for the 2025 financial year, show NOK 120.1m in revenue and NOK 36.1m in operating profit.

Key figures · 2025

Revenue
NOK 120.1m
Operating profit
NOK 36.1m
Equity
NOK 86.1m
Est. value
NOK 137.1m

Financial health · 2025

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

Who owns LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold?

No shareholders are registered for LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold

What is the revenue of LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold?

LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold had revenue of NOK 120.1m in 2025.

Where is LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold based?

LØVENSKIOLD-VÆKERØ Carl Otto Løvenskiold has its business address in Oslo.

Property

Business address Drammensveien 230, 0277 Oslo
Cadastral unit 301-7/78/0/0

4 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.