BIZTRAC BETA
Interior design activities

BETINAS DEKOR & STYLING AS

Org. no. 999120482 Limited company (AS) Horten Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 513,000
Operating profit NOK 709
Equity NOK 80,000
Incorporated 2012
Share capital NOK 30,000

BETINAS DEKOR & STYLING AS is registered as a limited company in Horten, Vestfold with organisation number 999120482. The business is classified under interior design activities (NACE 74.130). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 2000 shares. The company's stated purpose is: “Konsulenttjenester innen interiør og design samt salg av interiør artikler.”. The most recent filed accounts, for the 2024 financial year, show NOK 513,000 in revenue and NOK 709 in operating profit.

Key figures · 2024

Revenue
NOK 513,000
Operating profit
NOK 709
Equity
NOK 80,000
Est. value
NOK 52,000

Financial health · 2024

Liquidity
2.60
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
61.6%
Weak
Equity as a share of total capital

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

Who owns BETINAS DEKOR & STYLING AS?

BETINA OLSLUND
BETINAS DEKOR & STYLING AS
NOK 513,000 rev. · NOK 709 profit

BETINAS DEKOR & STYLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BETINAS DEKOR & STYLING AS

Who owns BETINAS DEKOR & STYLING AS?

BETINA OLSLUND is the largest registered owner, with 50.0%.

What is the revenue of BETINAS DEKOR & STYLING AS?

BETINAS DEKOR & STYLING AS had revenue of NOK 513,000 in 2024.

Who is the general manager of BETINAS DEKOR & STYLING AS?

Betina Olslund is registered as general manager of BETINAS DEKOR & STYLING AS.

Where is BETINAS DEKOR & STYLING AS based?

BETINAS DEKOR & STYLING AS has its business address in Skoppum.

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.