BIZTRAC BETA
Other recreational activities

SKJERKE BRYGGE AS

Org. no. 990329575 Limited company (AS) Bamble Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 227,000
Operating profit NOK 24,000
Equity NOK 199,000
Incorporated 2006
Share capital NOK 100,000

SKJERKE BRYGGE AS is registered as a limited company in Bamble, Telemark with organisation number 990329575. The business is classified under other recreational activities (NACE 93.292). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av båtplasser og båtopplag og alt som herved står i forbindelse, samt brøyting og veivedlikehold.”. The most recent filed accounts, for the 2025 financial year, show NOK 227,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2025

Revenue
NOK 227,000
Operating profit
NOK 24,000
Equity
NOK 199,000
Est. value
NOK 193,000

Financial health · 2025

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

Who owns SKJERKE BRYGGE AS?

MORTEN NYSTRAND
SKJERKE BRYGGE AS
NOK 227,000 rev. · NOK 24,000 profit

SKJERKE BRYGGE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKJERKE BRYGGE AS own?

SKJERKE BRYGGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKJERKE BRYGGE AS

Who owns SKJERKE BRYGGE AS?

MORTEN NYSTRAND is the largest registered owner, with 100.0%.

What is the revenue of SKJERKE BRYGGE AS?

SKJERKE BRYGGE AS had revenue of NOK 227,000 in 2025.

Who is the general manager of SKJERKE BRYGGE AS?

Morten Nystrand is registered as general manager of SKJERKE BRYGGE AS.

Where is SKJERKE BRYGGE AS based?

SKJERKE BRYGGE AS has its business address in Stathelle.

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.