BIZTRAC BETA
Rental and operating of own or leased real estate

ROAN BRYGGE-DRIFT AS

Org. no. 980123103 Limited company (AS) Åfjord Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 62,000
Operating profit NOK 3,000
Equity NOK 537,000
Incorporated 1998
Share capital NOK 485,000

ROAN BRYGGE-DRIFT AS is registered as a limited company in Åfjord, Trøndelag with organisation number 980123103. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1998. Registered share capital is NOK 485,000, divided into 485 shares. The company's stated purpose is: “Oppføring av bygg, produksjon, samt kjøp og salg. Selskapet kan selv eller i samarbeid med andre engasjere seg i virksomhet som står i sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 62,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2024

Revenue
NOK 62,000
Operating profit
NOK 3,000
Equity
NOK 537,000
Est. value
NOK 378,000

Financial health · 2024

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

Who owns ROAN BRYGGE-DRIFT AS?

KNUT KRISTIANSEN
ROAN BRYGGE-DRIFT AS
NOK 62,000 rev. · NOK 3,000 profit

ROAN BRYGGE-DRIFT AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROAN BRYGGE-DRIFT AS

Who owns ROAN BRYGGE-DRIFT AS?

KNUT KRISTIANSEN is the largest registered owner, with 49.9%.

What is the revenue of ROAN BRYGGE-DRIFT AS?

ROAN BRYGGE-DRIFT AS had revenue of NOK 62,000 in 2024.

Who is the general manager of ROAN BRYGGE-DRIFT AS?

Steinar Kristian Eian is registered as general manager of ROAN BRYGGE-DRIFT AS.

Where is ROAN BRYGGE-DRIFT AS based?

ROAN BRYGGE-DRIFT AS has its business address in Roan.

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.