BIZTRAC BETA
Computer programming activities

WEAVO AS

Org. no. 932918137 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK −165,000
Equity NOK −148,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−148k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−165k kr).

WEAVO AS is registered as a limited company in Oslo, Oslo with organisation number 932918137. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen programmering, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK −165,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK −165,000
Equity
NOK −148,000

Financial health · 2025

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

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

Who owns WEAVO AS?

BØHMER AS
WEAVO AS
NOK 1.8m rev. · NOK −165,000 profit

WEAVO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about WEAVO AS

Who owns WEAVO AS?

BØHMER AS is the largest registered owner, with 47.5%.

What is the revenue of WEAVO AS?

WEAVO AS had revenue of NOK 1.8m in 2025.

Who is the general manager of WEAVO AS?

Haakon Skavhaug-Flender is registered as general manager of WEAVO AS.

Where is WEAVO AS based?

WEAVO AS has its business address in Oslo.

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.