BIZTRAC BETA
Accounting and bookkeeping

STYREWEB REGNSKAP AS

Org. no. 821676282 Limited company (AS) Trondheim Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 93,000
Equity NOK 325,000
Incorporated 2018
Employees 8
Share capital NOK 100,000

STYREWEB REGNSKAP AS is registered as a limited company in Trondheim, Trøndelag with organisation number 821676282. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2018 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utførelse av regnskapstjenester for medlemsorganisasjoner samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 93,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 93,000
Equity
NOK 325,000
Est. value
NOK 624,000

Financial health · 2024

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.8%
Good
Equity as a share of total capital

Who owns STYREWEB REGNSKAP AS?

SPAREBANK 1 ØKONOMIPARTNER NORDMØRE AS
STYREWEB REGNSKAP AS
NOK 3.8m rev. · NOK 93,000 profit

STYREWEB REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STYREWEB REGNSKAP AS

Who owns STYREWEB REGNSKAP AS?

SPAREBANK 1 ØKONOMIPARTNER NORDMØRE AS is the largest registered owner, with 80.0%.

What is the revenue of STYREWEB REGNSKAP AS?

STYREWEB REGNSKAP AS had revenue of NOK 3.8m in 2024.

Who is the general manager of STYREWEB REGNSKAP AS?

Edvind Buberg is registered as general manager of STYREWEB REGNSKAP AS.

Where is STYREWEB REGNSKAP AS based?

STYREWEB REGNSKAP AS has its business address in Tiller.

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.