BIZTRAC BETA
Visual arts creation activities

OSBERG LASER ENGRAVER AS

Org. no. 936714005 Limited company (AS) Tønsberg Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 60,000
Incorporated 2025
Share capital NOK 60,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-11-21.

OSBERG LASER ENGRAVER AS is registered as a limited company in Tønsberg, Vestfold with organisation number 936714005. The business is classified under visual arts creation activities (NACE 90.120). The company was incorporated in 2025. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Lasergravering på ulike materialer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 60,000
Est. value
NOK 75,000

Financial health · 2025

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

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

Who owns OSBERG LASER ENGRAVER AS?

HENRIK ALEKSANDER BERG
OSBERG LASER ENGRAVER AS
NOK 0 rev. · NOK 0 profit

OSBERG LASER ENGRAVER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OSBERG LASER ENGRAVER AS

Who owns OSBERG LASER ENGRAVER AS?

HENRIK ALEKSANDER BERG is the largest registered owner, with 100.0%.

What is the revenue of OSBERG LASER ENGRAVER AS?

OSBERG LASER ENGRAVER AS had revenue of NOK 0 in 2025.

Who is the general manager of OSBERG LASER ENGRAVER AS?

Henrik Aleksander Berg is registered as general manager of OSBERG LASER ENGRAVER AS.

Where is OSBERG LASER ENGRAVER AS based?

OSBERG LASER ENGRAVER AS has its business address in Barkåker.

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.