BIZTRAC BETA
Manufacture of other builders' carpentry and joinery

REDDALSVEIEN 35 AS

Org. no. 991294953 Limited company (AS) Grimstad Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 2.1m
Equity NOK 8.7m
Incorporated 2007
Share capital NOK 2.9m

REDDALSVEIEN 35 AS is registered as a limited company in Grimstad, Agder with organisation number 991294953. The business is classified under manufacture of other builders' carpentry and joinery (NACE 16.230). The company was incorporated in 2007. Registered share capital is NOK 2.9m, divided into 100 shares. The company's stated purpose is: “Utvikle og drive fast eiendom ved utleie og eventuelt salg, samt delta i andre selskaper og alt som naturlig forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 2.1m in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 2.1m
Equity
NOK 8.7m
Est. value
NOK 8.2m

Financial health · 2024

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

Who owns REDDALSVEIEN 35 AS?

SØRLANDSLISTEN HOLDING AS
REDDALSVEIEN 35 AS
NOK 3.8m rev. · NOK 2.1m profit

REDDALSVEIEN 35 AS has 1 registered shareholder:

All shareholders and roles →

Group structure

REDDALSVEIEN 35 AS er morselskap for 3 datterselskaper:

Frequently asked questions about REDDALSVEIEN 35 AS

Who owns REDDALSVEIEN 35 AS?

SØRLANDSLISTEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of REDDALSVEIEN 35 AS?

REDDALSVEIEN 35 AS had revenue of NOK 3.8m in 2024.

Who is the general manager of REDDALSVEIEN 35 AS?

Kjetil Thoresen is registered as general manager of REDDALSVEIEN 35 AS.

Where is REDDALSVEIEN 35 AS based?

REDDALSVEIEN 35 AS has its business address in Grimstad.

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.