BIZTRAC BETA
Accounting and bookkeeping

Buskerud regnskapsdata AS

Org. no. 933902838 Limited company (AS) Drammen Incorporated 1983 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 43,000
Equity NOK 80,000
Incorporated 1983
Share capital NOK 100,000

Buskerud regnskapsdata AS is registered as a limited company in Drammen, Buskerud with organisation number 933902838. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1983. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive service innen dataregnskep og økonomi, og det som naturlig hører med.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 43,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 43,000
Equity
NOK 80,000
Est. value
NOK 217,000

Financial health · 2024

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

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

Who owns Buskerud regnskapsdata AS?

MARIANNE LINDBERG THEIE
Buskerud regnskapsdata AS
NOK 2.0m rev. · NOK 43,000 profit

Buskerud regnskapsdata AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about Buskerud regnskapsdata AS

Who owns Buskerud regnskapsdata AS?

MARIANNE LINDBERG THEIE is the largest registered owner, with 100.0%.

What is the revenue of Buskerud regnskapsdata AS?

Buskerud regnskapsdata AS had revenue of NOK 2.0m in 2024.

Who is the general manager of Buskerud regnskapsdata AS?

Marianne Lindberg Theie is registered as general manager of Buskerud regnskapsdata AS.

Where is Buskerud regnskapsdata AS based?

Buskerud regnskapsdata AS has its business address in Svelvik.

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.