biztrac. BETA
COMPANY REGISTER PROFILE
934940326 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and leasing of water transport equipment

RUNDEREIM BRYGGE AS

Org. no. 934940326 Limited company (AS) Stad Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 7,000
Operating profit NOK −4,000
Equity NOK 26,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

RUNDEREIM BRYGGE AS is registered as a limited company in Stad, Vestland with organisation number 934940326. The business is classified under rental and leasing of water transport equipment (NACE 77.340). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Utleige av båter til turer, fiske og annet som ligg naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 7,000
Operating profit
NOK −4,000
Equity
NOK 26,000
Est. value
NOK 17,000

Financial health · 2025

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

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

Who owns RUNDEREIM BRYGGE AS?

RUNDEREIM BRYGGE AS
NOK 7,000 rev. · NOK −4,000 profit

RUNDEREIM BRYGGE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RUNDEREIM BRYGGE AS

Who owns RUNDEREIM BRYGGE AS?

Stig André Lunde is the largest registered owner, with 50.0%.

What is the revenue of RUNDEREIM BRYGGE AS?

RUNDEREIM BRYGGE AS had revenue of NOK 7,000 in 2025.

Where is RUNDEREIM BRYGGE AS based?

RUNDEREIM BRYGGE AS has its business address in Selje.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.