BIZTRAC BETA
COMPANY REGISTER PROFILE
911696800 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

TRONES HYBELBYGG AS

Org. no. 911696800 Limited company (AS) Namsskogan Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −209,000
Equity NOK 145,000
Incorporated 2012
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−209k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRONES HYBELBYGG AS is registered as a limited company in Namsskogan, Trøndelag with organisation number 911696800. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom. Selskapet kan ha eierinteresser i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −209,000
▲ +12 %
Equity
NOK 145,000
▲ +144 %
Est. value
NOK 132,000

Financial health · 2025

Liquidity
8.67
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.2%
Satisfactory
Equity as a share of total capital

Who owns TRONES HYBELBYGG AS?

TRONES HYBELBYGG AS
· NOK −209,000 profit

TRONES HYBELBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRONES HYBELBYGG AS

Who owns TRONES HYBELBYGG AS?

MOEN HOLDING AS is the largest registered owner, with 100.0%.

Who is the general manager of TRONES HYBELBYGG AS?

Øistein Noralf Moen is registered as general manager of TRONES HYBELBYGG AS.

Where is TRONES HYBELBYGG AS based?

TRONES HYBELBYGG AS has its business address in Trones.

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

Report a problem

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