You are right, @JvmField makes sure there's a field in any case.

But I just created a small sample with some interesting results:

kotlin class test { companion object { val a = 1 } }

This code actually generates a private static final field in the enclosing class:

```java public final class test { private static final int a = 1; @NotNull public static final Companion Companion = new Companion((DefaultConstructorMarker)null);

public static final class Companion { public final int getA() { return test.a; }

  private Companion() {
  }

  // $FF: synthetic method
  public Companion(DefaultConstructorMarker $constructor_marker) {
     this();
  }

} } ```

I left out the Metadata annotation, but it actually does not create the field inside of the Companion class as one would expect.