BIZTRAC BETA
Activities of advertising agencies

JØSS BOKSTUDIO AS

Org. no. 815249542 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 502,000
Operating profit NOK −143,000
Equity NOK 171,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

JØSS BOKSTUDIO AS is registered as a limited company in Oslo, Oslo with organisation number 815249542. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å utvikle, produsere og formidle bøker, trykksaker, innhold og tilknyttede tjenester, samt virksomhet som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 502,000 in revenue and NOK −143,000 in operating profit.

Key figures · 2025

Revenue
NOK 502,000
Operating profit
NOK −143,000
Equity
NOK 171,000
Est. value
NOK 611,000

Financial health · 2025

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

Who owns JØSS BOKSTUDIO AS?

KRISTIN SAUGE
JØSS BOKSTUDIO AS
NOK 502,000 rev. · NOK −143,000 profit

JØSS BOKSTUDIO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about JØSS BOKSTUDIO AS

Who owns JØSS BOKSTUDIO AS?

KRISTIN SAUGE is the largest registered owner, with 33.3%.

What is the revenue of JØSS BOKSTUDIO AS?

JØSS BOKSTUDIO AS had revenue of NOK 502,000 in 2025.

Who is the general manager of JØSS BOKSTUDIO AS?

Marte Garmann is registered as general manager of JØSS BOKSTUDIO AS.

Where is JØSS BOKSTUDIO AS based?

JØSS BOKSTUDIO AS has its business address in Oslo.

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.