BIZTRAC BETA
Activities at camp schools

KYSTLEIRSKOLEN TVEDESTRAND AS

Org. no. 985512639 Limited company (AS) Tvedestrand Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 836,000
Equity NOK 1.7m
Incorporated 2002
Share capital NOK 100,000

KYSTLEIRSKOLEN TVEDESTRAND AS is registered as a limited company in Tvedestrand, Agder with organisation number 985512639. The business is classified under activities at camp schools (NACE 85.596). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Leirskole, kurs, utleie, kjøp og salg, fast eiendom samt beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 836,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 836,000
Equity
NOK 1.7m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns KYSTLEIRSKOLEN TVEDESTRAND AS?

PETER BRØYN SKUGGEVIK
KYSTLEIRSKOLEN TVEDESTRAND AS
NOK 4.8m rev. · NOK 836,000 profit

KYSTLEIRSKOLEN TVEDESTRAND AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KYSTLEIRSKOLEN TVEDESTRAND AS

Who owns KYSTLEIRSKOLEN TVEDESTRAND AS?

PETER BRØYN SKUGGEVIK is the largest registered owner, with 50.0%.

What is the revenue of KYSTLEIRSKOLEN TVEDESTRAND AS?

KYSTLEIRSKOLEN TVEDESTRAND AS had revenue of NOK 4.8m in 2024.

Who is the general manager of KYSTLEIRSKOLEN TVEDESTRAND AS?

Peter Brøyn Skuggevik is registered as general manager of KYSTLEIRSKOLEN TVEDESTRAND AS.

Where is KYSTLEIRSKOLEN TVEDESTRAND AS based?

KYSTLEIRSKOLEN TVEDESTRAND AS has its business address in Gjeving.

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.