BIZTRAC BETA
Construction of residential and non-residential buildings

OLSEN BRYGGESERVICE AS

Org. no. 935815525 Limited company (AS) Froland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 46,000
Equity NOK 66,000
Incorporated 2025
Share capital NOK 30,000

OLSEN BRYGGESERVICE AS is registered as a limited company in Froland, Agder with organisation number 935815525. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Håndverkstjenester, bygg tjenester og vedlikehold. Vaktmester tjenester. Bygging av brygger, verandaer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 46,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 46,000
Equity
NOK 66,000
Est. value
NOK 187,000

Financial health · 2025

Liquidity
0.57
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.3%
Weak
Equity as a share of total capital

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

Who owns OLSEN BRYGGESERVICE AS?

RAGNAR OLSEN
OLSEN BRYGGESERVICE AS
NOK 1.0m rev. · NOK 46,000 profit

OLSEN BRYGGESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLSEN BRYGGESERVICE AS

Who owns OLSEN BRYGGESERVICE AS?

RAGNAR OLSEN is the largest registered owner, with 100.0%.

What is the revenue of OLSEN BRYGGESERVICE AS?

OLSEN BRYGGESERVICE AS had revenue of NOK 1.0m in 2025.

Who is the general manager of OLSEN BRYGGESERVICE AS?

Ragnar Olsen is registered as general manager of OLSEN BRYGGESERVICE AS.

Where is OLSEN BRYGGESERVICE AS based?

OLSEN BRYGGESERVICE 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.