BIZTRAC BETA
Construction of residential and non-residential buildings

RONNY'S BYGG AS

Org. no. 918952470 Limited company (AS) Osen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 219,000
Equity NOK 1.2m
Incorporated 2017
Share capital NOK 200,000

RONNY'S BYGG AS is registered as a limited company in Osen, Trøndelag with organisation number 918952470. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2017. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Er å drive med entreprenørvirksomhet innen bygg og anlegg og tjenester som står i naturlig forbindelse med dette. Selskapet kan engasjere seg i annen virksomhet ved kjøp og salg av aksjer og verdipapirer, samt andre tiltak beslektet med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 219,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 219,000
Equity
NOK 1.2m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns RONNY'S BYGG AS?

RONNY OSEN
RONNY'S BYGG AS
NOK 3.2m rev. · NOK 219,000 profit

RONNY'S BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RONNY'S BYGG AS

Who owns RONNY'S BYGG AS?

RONNY OSEN is the largest registered owner, with 100.0%.

What is the revenue of RONNY'S BYGG AS?

RONNY'S BYGG AS had revenue of NOK 3.2m in 2025.

Who is the general manager of RONNY'S BYGG AS?

Ronny Osen is registered as general manager of RONNY'S BYGG AS.

Where is RONNY'S BYGG AS based?

RONNY'S BYGG AS has its business address in Steinsdalen.

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.