biztrac. BETA
COMPANY REGISTER PROFILE
928046206 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

BUVIKTIND AS

Org. no. 928046206 Limited company (AS) Bærum Incorporated 2021 Active
Revenue 2025 NOK 1.6m
Operating profit NOK −16,000
Equity NOK −677,000
Incorporated 2021
Share capital NOK 50,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−677k kr).

BUVIKTIND AS is registered as a limited company in Bærum, Akershus with organisation number 928046206. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Konsulentselskap samt handel med verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK −16,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
▲ +36 %
Operating profit
NOK −16,000
▲ +96 %
Equity
NOK −677,000
▲ +5 %

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
69.8%
Very good
Return on total assets
Solidity
-108.8%
Weak
Equity as a share of total capital

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

Who owns BUVIKTIND AS?

BUVIKTIND AS
NOK 1.6m rev. · NOK −16,000 profit

BUVIKTIND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUVIKTIND AS

Who owns BUVIKTIND AS?

Eirik Refstie is the largest registered owner, with 100.0%.

What is the revenue of BUVIKTIND AS?

BUVIKTIND AS had revenue of NOK 1.6m in 2025.

Who is the general manager of BUVIKTIND AS?

Eirik Refstie is registered as general manager of BUVIKTIND AS.

Where is BUVIKTIND AS based?

BUVIKTIND AS has its business address in Sandvika.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.