BIZTRAC BETA
Other education activities

KVITEBJØRN STASJON AS

Org. no. 990199507 Limited company (AS) Lunner Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 223,000
Operating profit NOK 25,000
Equity NOK 89,000
Incorporated 2006
Share capital NOK 100,000

KVITEBJØRN STASJON AS is registered as a limited company in Lunner, Akershus with organisation number 990199507. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Fremme forståelsen av uro som drivkraft for menneskelig atferd. Drive undervisning og kursvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 223,000 in revenue and NOK 25,000 in operating profit.

Key figures · 2025

Revenue
NOK 223,000
Operating profit
NOK 25,000
Equity
NOK 89,000
Est. value
NOK 179,000

Financial health · 2025

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

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

Who owns KVITEBJØRN STASJON AS?

ØYVIND KITTELSEN JOHANSEN
KVITEBJØRN STASJON AS
NOK 223,000 rev. · NOK 25,000 profit

KVITEBJØRN STASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KVITEBJØRN STASJON AS

Who owns KVITEBJØRN STASJON AS?

ØYVIND KITTELSEN JOHANSEN is the largest registered owner, with 100.0%.

What is the revenue of KVITEBJØRN STASJON AS?

KVITEBJØRN STASJON AS had revenue of NOK 223,000 in 2025.

Who is the general manager of KVITEBJØRN STASJON AS?

Øyvind Kittelsen Johansen is registered as general manager of KVITEBJØRN STASJON AS.

Where is KVITEBJØRN STASJON AS based?

KVITEBJØRN STASJON AS has its business address in Lunner.

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.