biztrac. BETA
COMPANY REGISTER PROFILE
931576593 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of furniture and home furnishings

BARBRO BEKKEN AS

Org. no. 931576593 Limited company (AS) Sel Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 830,000
Operating profit NOK 18,000
Equity NOK 53,000
Incorporated 2023
Share capital NOK 30,000

BARBRO BEKKEN AS is registered as a limited company in Sel, Innlandet with organisation number 931576593. The business is classified under repair and maintenance of furniture and home furnishings (NACE 95.240). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utforming av visuelle effekter for scene, møbeltapetsering.”. The most recent filed accounts, for the 2025 financial year, show NOK 830,000 in revenue and NOK 18,000 in operating profit.

Key figures · 2025

Revenue
NOK 830,000
▲ +77 %
Operating profit
NOK 18,000
▼ −7 %
Equity
NOK 53,000
▲ +38 %
Est. value
NOK 90,000

Financial health · 2025

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
14.1%
Good
Return on total assets
Solidity
25.3%
Weak
Equity as a share of total capital

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

Who owns BARBRO BEKKEN AS?

BARBRO BEKKEN AS
NOK 830,000 rev. · NOK 18,000 profit

BARBRO BEKKEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BARBRO BEKKEN AS

Who owns BARBRO BEKKEN AS?

Barbro Bekken is the largest registered owner, with 100.0%.

What is the revenue of BARBRO BEKKEN AS?

BARBRO BEKKEN AS had revenue of NOK 830,000 in 2025.

Who is the general manager of BARBRO BEKKEN AS?

Barbro Bekken is registered as general manager of BARBRO BEKKEN AS.

Where is BARBRO BEKKEN AS based?

BARBRO BEKKEN AS has its business address in Otta.

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.