BIZTRAC BETA
Joinery installation

RØNNINGEN & BAARDSEN AS

Org. no. 934845668 Limited company (AS) Froland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 319,000
Operating profit NOK 45,000
Equity NOK 60,000
Incorporated 2025
Share capital NOK 30,000

RØNNINGEN & BAARDSEN AS is registered as a limited company in Froland, Agder with organisation number 934845668. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Snekker og vaktmesteren. Transport. Bemanning. Kjøp, salg, utleie av verktøy, tilhengere og kjøretøy.”. The most recent filed accounts, for the 2025 financial year, show NOK 319,000 in revenue and NOK 45,000 in operating profit.

Key figures · 2025

Revenue
NOK 319,000
Operating profit
NOK 45,000
Equity
NOK 60,000
Est. value
NOK 165,000

Financial health · 2025

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

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

Who owns RØNNINGEN & BAARDSEN AS?

RICHARD RØNNINGEN
RØNNINGEN & BAARDSEN AS
NOK 319,000 rev. · NOK 45,000 profit

RØNNINGEN & BAARDSEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØNNINGEN & BAARDSEN AS

Who owns RØNNINGEN & BAARDSEN AS?

RICHARD RØNNINGEN is the largest registered owner, with 50.0%.

What is the revenue of RØNNINGEN & BAARDSEN AS?

RØNNINGEN & BAARDSEN AS had revenue of NOK 319,000 in 2025.

Who is the general manager of RØNNINGEN & BAARDSEN AS?

Richard Rønningen is registered as general manager of RØNNINGEN & BAARDSEN AS.

Where is RØNNINGEN & BAARDSEN AS based?

RØNNINGEN & BAARDSEN AS has its business address in Froland.

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.