BIZTRAC BETA
Computer programming activities

WEBRODENT AS

Org. no. 929482387 Limited company (AS) Porsgrunn Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 147,000
Operating profit NOK 66,000
Equity NOK 46,000
Incorporated 2022
Share capital NOK 30,000

WEBRODENT AS is registered as a limited company in Porsgrunn, Telemark with organisation number 929482387. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg og rådgivning innen IT og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 147,000 in revenue and NOK 66,000 in operating profit.

Key figures · 2025

Revenue
NOK 147,000
Operating profit
NOK 66,000
Equity
NOK 46,000
Est. value
NOK 253,000

Financial health · 2025

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

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

Who owns WEBRODENT AS?

INVEST-LIA AS
WEBRODENT AS
NOK 147,000 rev. · NOK 66,000 profit

WEBRODENT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about WEBRODENT AS

Who owns WEBRODENT AS?

INVEST-LIA AS is the largest registered owner, with 33.4%.

What is the revenue of WEBRODENT AS?

WEBRODENT AS had revenue of NOK 147,000 in 2025.

Who is the general manager of WEBRODENT AS?

Øyvind Brakstad is registered as general manager of WEBRODENT AS.

Where is WEBRODENT AS based?

WEBRODENT AS has its business address in Porsgrunn.

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.