BIZTRAC BETA
Computer consultancy and computer facilities management activities

ROBUZT AS

Org. no. 933006913 Limited company (AS) Larvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 545,000
Operating profit NOK 500,000
Equity NOK 33,000
Incorporated 2024
Share capital NOK 30,000

ROBUZT AS is registered as a limited company in Larvik, Vestfold with organisation number 933006913. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av varer og tjenester innen produksjon og drift av digitale løsninger og annet som naturlig hører sammen med dette, samt investering og deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 545,000 in revenue and NOK 500,000 in operating profit.

Key figures · 2025

Revenue
NOK 545,000
Operating profit
NOK 500,000
Equity
NOK 33,000
Est. value
NOK 1.6m

Financial health · 2025

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

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

Who owns ROBUZT AS?

LARS BREVIK
ROBUZT AS
NOK 545,000 rev. · NOK 500,000 profit

ROBUZT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROBUZT AS

Who owns ROBUZT AS?

LARS BREVIK is the largest registered owner, with 50.0%.

What is the revenue of ROBUZT AS?

ROBUZT AS had revenue of NOK 545,000 in 2025.

Who is the general manager of ROBUZT AS?

Lars Brevik is registered as general manager of ROBUZT AS.

Where is ROBUZT AS based?

ROBUZT AS has its business address in Tjodalyng.

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.