BIZTRAC BETA
Intermediation service activities for real estate activities

BOVG TAKST AS

Org. no. 935349877 Limited company (AS) Drammen Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 412,000
Equity NOK 324,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BOVG TAKST AS is registered as a limited company in Drammen, Buskerud with organisation number 935349877. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Tilby rådgivning og taksering av eiendom. Selskapet kan også kjøpe og selge aksjer, samt delta i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 412,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 412,000
Equity
NOK 324,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns BOVG TAKST AS?

BOVG GROUP AS
BOVG TAKST AS
NOK 2.4m rev. · NOK 412,000 profit

BOVG TAKST AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BOVG TAKST AS

Who owns BOVG TAKST AS?

BOVG GROUP AS is the largest registered owner, with 80.0%.

What is the revenue of BOVG TAKST AS?

BOVG TAKST AS had revenue of NOK 2.4m in 2025.

Who is the general manager of BOVG TAKST AS?

Martin Veierland is registered as general manager of BOVG TAKST AS.

Where is BOVG TAKST AS based?

BOVG TAKST AS has its business address in Drammen.

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.