BIZTRAC BETA
Rental and operating of own or leased real estate

BETONG AS

Org. no. 916896689 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 276,000
Operating profit NOK −111,000
Equity NOK −840,000
Incorporated 2016
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−840k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−111k kr).

BETONG AS is registered as a limited company in Oslo, Oslo with organisation number 916896689. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fremleie til selvstendige innen frisør- og hudpleievirksomhet”. The most recent filed accounts, for the 2025 financial year, show NOK 276,000 in revenue and NOK −111,000 in operating profit.

Key figures · 2025

Revenue
NOK 276,000
Operating profit
NOK −111,000
Equity
NOK −840,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1167127.8%
Weak
Equity as a share of total capital

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

Who owns BETONG AS?

CLAUDIA ANDREA NUNEZ GODOY
BETONG AS
NOK 276,000 rev. · NOK −111,000 profit

BETONG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BETONG AS

Who owns BETONG AS?

CLAUDIA ANDREA NUNEZ GODOY is the largest registered owner, with 100.0%.

What is the revenue of BETONG AS?

BETONG AS had revenue of NOK 276,000 in 2025.

Who is the general manager of BETONG AS?

Claudia Andrea Nunez Godoy is registered as general manager of BETONG AS.

Where is BETONG AS based?

BETONG AS has its business address in Oslo.

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.